Bug 691200 - Convert fence-virt to use QMFv2
Summary: Convert fence-virt to use QMFv2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fence-virt
Version: 6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Zane Bitter
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 571805
TreeView+ depends on / blocked
 
Reported: 2011-03-27 14:39 UTC by Perry Myers
Modified: 2011-12-06 11:37 UTC (History)
6 users (show)

Fixed In Version: fence-virt-0.2.3-3.el6
Doc Type: Bug Fix
Doc Text:
Do not document.
Clone Of: 688200
Environment:
Last Closed: 2011-12-06 11:37:59 UTC
Target Upstream Version:


Attachments (Terms of Use)
Configuration file for fence_virtd (386 bytes, text/plain)
2011-11-15 00:55 UTC, Lon Hohberger
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1566 0 normal SHIPPED_LIVE fence-virt bug fix and enhancement update 2011-12-06 00:39:10 UTC

Description Perry Myers 2011-03-27 14:39:43 UTC
Description of problem:
fence-virt currently uses QMFv1.  It needs to be updated to QMFv2

Comment 5 Lon Hohberger 2011-08-11 01:11:45 UTC
Patches look good; do we want to update the config file stuff (I'll do it), or will it just work as-is ?

Comment 6 Lon Hohberger 2011-08-11 01:41:43 UTC
Nevermind, looks like the config is compatible so we'll leave it alone.

Comment 11 Lon Hohberger 2011-10-26 22:17:19 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Do not document.

Comment 12 Lon Hohberger 2011-11-15 00:55:37 UTC
Created attachment 533656 [details]
Configuration file for fence_virtd

I used the attached configuration when attempting to run.  Without specifically setting the host and/or port, fence_virtd crashed, which will be a bug we need to address later.

I started qpidd with the following options:

  --auth no -m yes

I started libvirt-qmf with the following options:

  --broker localhost -p 5672 -d

Starting fence_virtd in the foreground allowed me to watch the following occur:

ipv4_recv_sk: success, fd = 5
Request 2 seqno 955657 domain f16-1
Plain TCP request
ipv4_connect: Connecting to client
ipv4_connect: Success; fd = 6
tcp_response: no-op (AUTH_NONE)
tcp_challenge: no-op (AUTH_NONE)
Request 2 seqno 955657 src 127.0.0.1 target f16-1
[libvirt-qpid] REBOOT operation on f16-1
[libvirt-qpid] OFF operation on f16-1
f16-1 running
2011-11-14 19:51:12 warning Connection [127.0.0.1:59733-127.0.0.1:5672] closed
[libvirt-qpid] ON operation on f16-1
f16-1 shutoff
2011-11-14 19:51:15 warning Connection [127.0.0.1:59734-127.0.0.1:5672] closed
Sending response to caller...

On the caller side:
[root@zealand lhh]# fence_xvm -o reboot -H f16-1
Could not read /etc/cluster/fence_xvm.key; trying without authentication
[root@zealand lhh]# echo $?
0

On the VM side, I observed the virtual machine move to the powered-off state then restart itself.

Comment 13 Lon Hohberger 2011-11-15 01:13:16 UTC
I tracked down the crash to a port not being specified; it is possible a simple port change will cause things to work as expected (though it is likely libvirt-qpid.cpp should handle the exception being thrown by the QMF API)

https://bugzilla.redhat.com/show_bug.cgi?id=753974

Comment 15 errata-xmlrpc 2011-12-06 11:37:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1566.html


Note You need to log in before you can comment on or make changes to this bug.