[ovirt-users] oVirt power management issue

Sun Dec 7 23:14:54 UTC 2014

----- Original Message -----
> From: "Wout Peeters" <wout at unix-solutions.be>
> To: users at ovirt.org
> Sent: Friday, December 5, 2014 12:50:24 PM
> Subject: [ovirt-users] oVirt power management issue
> 
> Hi,
> 
> We're trying to set up an oVirt configuration with an oVirt-controller
> (CentOS 6), iSCSI-storage (Dell MD3200i) and 3 vm-hosts (CentOS 7) powered
> by 2 APC PDUs. Testing the Power Management settings in the web GUI, we get
> the following message: "Test Succeeded, unknown." The oVirt engine log
> outputs the following:
> 
> 2014-12-05 11:23:00,872 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-7) Correlation ID: null, Call Stack: null, Custom Event
> ID: -1, Message: Host vm-02 from data center XXXX was chosen as a proxy to
> execute Status command on Host vm-03.
> 2014-12-05 11:23:00,879 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (ajp--127.0.0.1-8702-7) Using Host vm-02 from data center XXXX as proxy to
> execute Status command on Host
> 2014-12-05 11:23:00,904 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (ajp--127.0.0.1-8702-7) Executing <Status> Power Management command, Proxy
> Host:vm-02, Agent:apc, Target Host:, Management IP:***.***.***.***,
> User:apc, Options:, Fencing policy:null
> 2014-12-05 11:23:00,930 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (ajp--127.0.0.1-8702-7) START, FenceVdsVDSCommand(HostName = vm-02, HostId =
> 071554fc-eed2-4e8f-b6bc-041248d0eaa5, targetVdsId =
> 67c642ed-0a7a-4e3b-8dd6-32a36df4aea9, action = Status, ip = ***.***.***.***,
> port = , type = apc, user = apc, password = ******, options = '', policy =
> 'null'), log id: 2803522
> 2014-12-05 11:23:01,137 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-7) Correlation ID: null, Call Stack: null, Custom Event
> ID: -1, Message: Power Management test failed for Host vm-03.Done
> 2014-12-05 11:23:01,138 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (ajp--127.0.0.1-8702-7) FINISH, FenceVdsVDSCommand, return: Test Succeeded,
> unknown, log id: 2803522
> 2014-12-05 11:23:01,139 WARN [org.ovirt.engine.core.bll.FenceExecutor]
> (ajp--127.0.0.1-8702-7) Fencing operation failed with proxy host
> 071554fc-eed2-4e8f-b6bc-041248d0eaa5, trying another proxy...
> 2014-12-05 11:23:01,241 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-7) Correlation ID: null, Call Stack: null, Custom Event
> ID: -1, Message: Host vm-01 from data center XXXX was chosen as a proxy to
> execute Status command on Host vm-03.
> 2014-12-05 11:23:01,244 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (ajp--127.0.0.1-8702-7) Using Host vm-01 from data center XXXX as proxy to
> execute Status command on Host
> 2014-12-05 11:23:01,246 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (ajp--127.0.0.1-8702-7) Executing <Status> Power Management command, Proxy
> Host:vm-01, Agent:apc, Target Host:, Management IP:***.***.***.***,
> User:apc, Options:, Fencing policy:null
> 2014-12-05 11:23:01,273 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (ajp--127.0.0.1-8702-7) START, FenceVdsVDSCommand(HostName = vm-01, HostId =
> c50eb9bf-5294-4d46-813d-7adfcb41d71d, targetVdsId =
> 67c642ed-0a7a-4e3b-8dd6-32a36df4aea9, action = Status, ip = ***.***.***.***,
> port = , type = apc, user = apc, password = ******, options = '', policy =
> 'null'), log id: 2b00de15
> 2014-12-05 11:23:01,449 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-7) Correlation ID: null, Call Stack: null, Custom Event
> ID: -1, Message: Power Management test failed for Host vm-03.Done
> 2014-12-05 11:23:01,451 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (ajp--127.0.0.1-8702-7) FINISH, FenceVdsVDSCommand, return: Test Succeeded,
> unknown, log id: 2b00de15
> 
> This is the vdsm.log output:
> 
> JsonRpc (StompReactor)::DEBUG::2014-12-05
> 11:34:05,065::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling
> message <StompFrame command='SEND'>
> JsonRpcServer::DEBUG::2014-12-05
> 11:34:05,067::__init__::504::jsonrpc.JsonRpcServer::(serve_requests) Waiting
> for request
> Thread-24996::DEBUG::2014-12-05 11:34:05,069::API::1188::vds::(fenceNode)
> fenceNode(addr=***.***.***.***,port=,agent=apc,user=apc,passwd=XXXX,action=status,secure=False,options=,policy=None)
> Thread-24996::DEBUG::2014-12-05 11:34:05,069::utils::738::root::(execCmd)
> /usr/sbin/fence_apc (cwd None)
> Thread-24996::DEBUG::2014-12-05 11:34:05,131::utils::758::root::(execCmd)
> FAILED: <err> = "Failed: You have to enter plug number or machine
> identification\nPlease use '-h' for usage\n"; <rc> = 1
> Thread-24996::DEBUG::2014-12-05 11:34:05,131::API::1143::vds::(fence) rc 1
> inp agent=fence_apc
> ipaddr=***.***.***.***
> login=apc
> action=status
> passwd=XXXX
> out [] err ['Failed: You have to enter plug number or machine
> identification', "Please use '-h' for usage"]
> 
> The 'port' and 'options' fields show up as empty, even if we enter '22' or
> 'port=22'. We did enter the slot number as well.
> 
> Entering the fence_apc command manually, we get:
> 
> fence_apc -a ***.***.***.*** -l apc -p ****** -o status -n 1 -x
> Status: ON
> 
> Anyone have an idea what could be the problem?

Hi, first please attach a full engine log and vdsm.log on the machine that served as a proxy for this operation
Please also attach the result of the following on the machine that served as a proxy for this operation

rpm -qa | grep vdsm
rpm -qa | grep fence-agents 

Is that a PowerPC machine ???

Thanks
Eli Mesika 

> 
> 
> Thanks for your time and kind regards,
> 
> Wout
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 