I've tried to add "port=1" to the Options field but that seems to have no effect.

From: "Ian Levesque" <ian(a)crystal.harvard.edu&gt; To: users(a)ovirt.org Sent: Friday, April 20, 2012 6:36:16 PM Subject: [Users] high availability via fencing Hello, I'm testing ovirt for potential deployment and one of the metrics for its success relies on the high availability feature. In my research on this feature, I found scattered documentation indicating that fencing is a prerequisite. On my test hardware, I don't have any LOM/IPMI but I see that APC managed PDUs are supported, which I do have. The problem is when I try to configure Power Management to use the "apc" type, I get this error: Test Failed, Host Status is: unknown. The fence-agent script reported the following error: Failed: You have to enter plug number Please use '-h' for usage ovirt-engine/engine.log tells me: 2012-04-20 11:32:44,595 INFO [org.ovirt.engine.core.bll.FencingExecutor] (http--0.0.0.0-8443-5) Executing <Status> Power Management command, Proxy Host:heilig, Agent:apc, Target Host:, Management IP:134.174.x.x, User:ovirt, Options:port=22,secure=true,slot=1 2012-04-20 11:32:44,598 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (http--0.0.0.0-8443-5) START, FenceVdsVDSCommand(vdsId = 6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId = 60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip = 134.174.x.x, port = , type = apc, user = ovirt, password = ******, options = 'port=22,secure=true,slot=1'), log id: 57f86a56 2012-04-20 11:32:44,696 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test Failed, Host Status is: unknown. The fence-agent script reported the following error: Failed: You have to enter plug number Please use '-h' for usage I've tried to add "port=1" to the Options field but that seems to have no effect. Any ideas? Is there any way to configure a "dumb" power management / fencing configuration for testing?

Cheers, Ian _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

>> 2012-04-20 11:32:44,696 INFO >> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] >> (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test >> Failed, Host Status is: unknown. The fence-agent script reported the >> following error: Failed: You have to enter plug number >> Please use '-h' for usage >> >> I've tried to add "port=1" to the Options field but that seems to >> have no effect. >> >> Any ideas? Is there any way to configure a "dumb" power management / >> fencing configuration for testing? > > If you still have the problem, can you please put also the vdsm log (look for "fenceNode" ) > Thanks Hi Eli, Here is the relevant output, though I don't think it'll be much more help:

Thread-1818::DEBUG::2012-04-24 12:17:59,804::API::954::vds::(fenceNode) fenceNode(addr=134.174.x.x,port=,agent=apc,user=ovirt,passwd=XXXX,action=status,secure=,options=) Thread-1818::DEBUG::2012-04-24 12:17:59,841::API::980::vds::(fenceNode) rc 1 in agent=fence_apc ipaddr=134.174.x.x login=ovirt option=status passwd=XXXX out err Failed: You have to enter plug number Please use '-h' for usage Thanks, Ian _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

----- Original Message ----- > From: "Dan Kenigsberg" <danken(a)redhat.com&gt; > To: "Ian Levesque" <ian(a)crystal.harvard.edu&gt; > Cc: "Eli Mesika" <emesika(a)redhat.com&gt;, users(a)ovirt.org > Sent: Wednesday, April 25, 2012 7:59:08 AM > Subject: Re: [Users] high availability via fencing > > On Tue, Apr 24, 2012 at 12:20:37PM -0400, Ian Levesque wrote: > > >> 2012-04-20 11:32:44,696 INFO > > >> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] > > >> (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test > > >> Failed, Host Status is: unknown. The fence-agent script reported > > >> the > > >> following error: Failed: You have to enter plug number > > >> Please use '-h' for usage > > >> > > >> I've tried to add "port=1" to the Options field but that seems > > >> to > > >> have no effect. > > >> > > >> Any ideas? Is there any way to configure a "dumb" power > > >> management / > > >> fencing configuration for testing? > > > > > > If you still have the problem, can you please put also the vdsm > > > log (look for "fenceNode" ) > > > Thanks > > > > Hi Eli, > > > > Here is the relevant output, though I don't think it'll be much > > more help: > > Actually, it does, since it shows that Vdsm did not receive any > 'port' > to pass to fence_apc, which is required. 'port' is usually the > ordinal > postion of your blade. Either define it in the GUI or use port=<n> > option in the options edit box. This is the line from the engine log 2012-04-20 11:32:44,598 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (http--0.0.0.0-8443-5) START, FenceVdsVDSCommand(vdsId = 6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId = 60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip = 134.174.x.x, port = , type = apc, user = ovirt, password = ******, options = 'port=22,secure=true,slot=1'), log id: 57f86a56 So, what I see is that port was sent twice , once as empty and then the port=22 is sent as part of the options string. Can you please remove the port from the options field and put it in the port field. If this works , this is an engine core bug...

>> So, what I see is that port was sent twice , once as empty and then the port=22 is sent as part of the options string. >> >> Can you please remove the port from the options field and put it in the port field. >> If this works , this is an engine core bug... > > I believe that it is such a bug, since the "options" field come up as > empty in vdsm. I tried entering a Port, Slot and "plug=1" in options. I also checked "Secure". It indeed appears that the engine isn't passing the options along. I also find it odd that a required field (plug) isn't available via a form field. Is that just a side effect? I can file a bug -- does it belong in ovirt-engine-core?