Created attachment 982652[details]
log from rhevm shell
Description of problem:
3 new rhev-h6.6 machines registered/not yet approved to rhevm via TUI.
In rhevm during approving machine, I setup up power management for 1st host, RHEVM is trying to test fencing via 2nd machine, which is not yet approved. Test for power management is time-outing.
Version-Release number of selected component (if applicable):
3.5.0-0.30.el6ev
How reproducible:
100%
Steps to Reproduce:
1. Register several rhev-h via TUI ( do not approve them in REHVM )
2. Click on 1st for approval and setup power management during approval phase, confirm dialog.
3. See dialog have work in-progress - window is waiting for test timeout before closing.
Actual results:
RHEVM is trying to test fencing via 2nd machine, which is not yet approved.
Expected results:
not use non-approved host for fencing tests.
Additional info: Host added, but dialog is stucked for 5-6 minutes to wait for fencing test to timeout. Who will be so patient, when he has not info whatsoever is in progress?
Part of engine log:
2015-01-22 09:07:25,821 INFO [org.ovirt.engine.core.bll.FenceExecutor] (ajp-/127.0.0.1:8702-1) [746f9f51] Executing <Status> Power Management command, Proxy Host:slot-10.rhev.lab.eng.brq.redhat.com, Agent:ipmilan, Target Host:dell-r210ii-16.rhev.lab.eng.brq.redhat.com, Management IP:10.34.62.158, User:root, Options:, Fencing policy:null
2015-01-22 09:07:25,822 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp-/127.0.0.1:8702-1) [746f9f51] START, FenceVdsVDSCommand(HostName = slot-10.rhev.lab.eng.brq.redhat.com, HostId = ce969a71-ffab-499b-b783-9352ed041267, targetVdsId = 320af8a2-fa19-4650-a8fc-c4987a7d2587, action = Status, ip = 10.34.62.158, port = , type = ipmilan, user = root, password = ******, options = '', policy = 'null'), log id: 55e5ace
2015-01-22 09:07:25,824 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) Connecting to /10.34.63.140
2015-01-22 09:07:25,833 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) Unable to process messages
2015-01-22 09:07:25,834 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) Connecting to /10.34.63.140
2015-01-22 09:07:25,850 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) Unable to process messages
2015-01-22 09:10:28,036 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp-/127.0.0.1:8702-2) FINISH, FenceVdsVDSCommand, return: Test Failed, Message timeout which can be caused by communication issues, log id: 7b609b01
Created attachment 982652 [details] log from rhevm shell Description of problem: 3 new rhev-h6.6 machines registered/not yet approved to rhevm via TUI. In rhevm during approving machine, I setup up power management for 1st host, RHEVM is trying to test fencing via 2nd machine, which is not yet approved. Test for power management is time-outing. Version-Release number of selected component (if applicable): 3.5.0-0.30.el6ev How reproducible: 100% Steps to Reproduce: 1. Register several rhev-h via TUI ( do not approve them in REHVM ) 2. Click on 1st for approval and setup power management during approval phase, confirm dialog. 3. See dialog have work in-progress - window is waiting for test timeout before closing. Actual results: RHEVM is trying to test fencing via 2nd machine, which is not yet approved. Expected results: not use non-approved host for fencing tests. Additional info: Host added, but dialog is stucked for 5-6 minutes to wait for fencing test to timeout. Who will be so patient, when he has not info whatsoever is in progress? Part of engine log: 2015-01-22 09:07:25,821 INFO [org.ovirt.engine.core.bll.FenceExecutor] (ajp-/127.0.0.1:8702-1) [746f9f51] Executing <Status> Power Management command, Proxy Host:slot-10.rhev.lab.eng.brq.redhat.com, Agent:ipmilan, Target Host:dell-r210ii-16.rhev.lab.eng.brq.redhat.com, Management IP:10.34.62.158, User:root, Options:, Fencing policy:null 2015-01-22 09:07:25,822 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp-/127.0.0.1:8702-1) [746f9f51] START, FenceVdsVDSCommand(HostName = slot-10.rhev.lab.eng.brq.redhat.com, HostId = ce969a71-ffab-499b-b783-9352ed041267, targetVdsId = 320af8a2-fa19-4650-a8fc-c4987a7d2587, action = Status, ip = 10.34.62.158, port = , type = ipmilan, user = root, password = ******, options = '', policy = 'null'), log id: 55e5ace 2015-01-22 09:07:25,824 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) Connecting to /10.34.63.140 2015-01-22 09:07:25,833 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) Unable to process messages 2015-01-22 09:07:25,834 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) Connecting to /10.34.63.140 2015-01-22 09:07:25,850 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) Unable to process messages 2015-01-22 09:10:28,036 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp-/127.0.0.1:8702-2) FINISH, FenceVdsVDSCommand, return: Test Failed, Message timeout which can be caused by communication issues, log id: 7b609b01