Bug 1219620

Description of problem:

After upgrading from engine running CentOS 7 and ovirt node 3.5.1 to engine running on CentOS 7.1 and CentOS 7.1 hosts as "nodes", fencing with idrac7 no longer works.

Steps to Reproduce:
1. Add 2 new hosts to engine configured with idrac7 power management (no longer need to specify options for idrac7 with 3.5.2 - thank you.).
2. Click "Test" button on Power Management page.
3. "Test Succeeded, unknown".

It didn't really succeed at all.

engine:

2015-05-07 15:19:37,585 INFO  [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-1) Using Host virt1 from cluster EECS-Primary as proxy to execute Status command on Host 
2015-05-07 15:19:37,587 INFO  [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-1) Executing <Status> Power Management command, Proxy Host:virt1, Agent:ipmilan, Target Host:, Management IP:virt2-idrac, User:root, Options:privlvl=OPERATOR,lanplus,delay=10, Fencing policy:null
2015-05-07 15:19:37,602 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp--127.0.0.1-8702-1) START, FenceVdsVDSCommand(HostName = virt1, HostId = 6a638c0a-0a48-4e77-81b5-f89ae572cf3e, targetVdsId = 8df66929-0cb7-4347-b004-c5531178d024, action = Status, ip = virt2-idrac, port = , type = ipmilan, user = root, password = ******, options = 'privlvl=OPERATOR,lanplus,delay=10', policy = 'null'), log id: 682d66b2
2015-05-07 15:19:53,876 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-1) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Power Management test failed for Host virt2.Done
2015-05-07 15:19:53,876 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp--127.0.0.1-8702-1) FINISH, FenceVdsVDSCommand, return: Test Succeeded, unknown, log id: 682d66b2

on virt1 vdsm log:

hread-11121::DEBUG::2015-05-07 15:19:53,864::API::1164::vds::(fence) rc 1 inp agent=fence_ipmilan
ipaddr=virt2-idrac
login=root
action=status
passwd=XXXX
privlvl=OPERATOR
delay=10
lanplus out [] err ['Failed: Unable to obtain correct plug status or plug is not available', '', '']
Thread-11121::DEBUG::2015-05-07 15:19:53,864::API::1235::vds::(fenceNode) rc 1 in agent=fence_ipmilan
ipaddr=virt2-idrac
login=root
action=status
passwd=XXXX
privlvl=OPERATOR
delay=10
lanplus out [] err ['Failed: Unable to obtain correct plug status or plug is not available', '', '']

We can see that engine was able to contact virt1.
virt1 was able to contact virt2-idrac.
Password is correct.

I know that fence_ipmilan works successfully because I can go to virt2 and run the following:

/usr/sbin/fence_ipmilan -a virt1-idrac -l root -o status -p 'my-password' -L OPERATOR -P

The result is "Status: ON" as it was with 3.5.1.

Likewise, I can make virt1 verify virt2-idrac manually:

/usr/sbin/fence_ipmilan -a virt2-idrac -l root -o status -p 'my-password' -L OPERATOR -P 

Again, "Status: ON".

I've seen this "Test Succeeded, unknown" previously while getting the options right for idrac7 with 3.5.1.  The error needs to be corrected as well.  In this case, it was a failure.