From: Zane Bitter <zbitter@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Fix error getting status from libvirt-qpid plugin
Date: Mon, 01 Aug 2011 18:36:18 +0200 [thread overview]
Message-ID: <20110801163602.2120.63669.stgit@zbitter.fedora> (raw)
Signed-off-by: Zane Bitter <zbitter@redhat.com>
---
server/libvirt-qpid.cpp | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/server/libvirt-qpid.cpp b/server/libvirt-qpid.cpp
index 593f47c..4a3dc17 100644
--- a/server/libvirt-qpid.cpp
+++ b/server/libvirt-qpid.cpp
@@ -170,7 +170,7 @@ do_lq_request(struct lq_info *info, const char *vm_name,
i = 0;
}
- if (!strcasecmp(action, "status")) {
+ if (!strcasecmp(action, "state")) {
result.code = i;
goto out;
}
@@ -246,7 +246,7 @@ lq_status(const char *vm_name, void *priv)
VALIDATE(priv);
printf("[libvirt-qpid] STATUS operation on %s\n", vm_name);
- return do_lq_request((lq_info *)priv, vm_name, "destroy");
+ return do_lq_request((lq_info *)priv, vm_name, "state");
}
next reply other threads:[~2011-08-01 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 16:36 Zane Bitter [this message]
2011-08-02 15:10 ` [Cluster-devel] [PATCH] Fix error getting status from libvirt-qpid plugin Lon Hohberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110801163602.2120.63669.stgit@zbitter.fedora \
--to=zbitter@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).