[Users] high availability via fencing

[Dan Kenigsberg]

On Wed, Apr 25, 2012 at 05:13:40AM -0400, Eli Mesika wrote:
> 
> 
> ----- Original Message -----
> > From: "Dan Kenigsberg" <danken at redhat.com>
> > To: "Ian Levesque" <ian at crystal.harvard.edu>
> > Cc: "Eli Mesika" <emesika at redhat.com>, users at 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...

I believe that it is such a bug, since the "options" field come up as
empty in vdsm.