Description of problem: Currently it's not obvious why a fencing event occucred. To give the user a hint it would be better to display/gather more informations about the fencing events. This would also help GSS to analyze the incident.
Eli please make sure we have the folowing in the event log: - host enetered connecting status (+ timeout calculated) - host became non-responsive - all the fencing attempts (including the proxy selected) Ar
*** Bug 1090520 has been marked as a duplicate of this bug. ***
attempt to verify with ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch. 1. install 2 hosts, at least 1 with pm. 2. stop network for host with pm. 3.verify all the messages as described in comment #1 are issued. failed: regarding the new message added in this patch: VDS_HOST_NOT_RESPONDING_CONNECTING=Host ${VdsName} is not responding. It will stay in Connecting sta te for a grace period of ${Seconds} seconds and after that an attempt to fence the host will be issu ed. the message appears in engine.log but not issued in events in ui. from engine.log: 2014-08-21 14:54:30,194 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-69) Host {hostname} is not responding. It will stay in Connecting state for a grace period of $120 seconds and after that an attempt to fence the host will be issued.
Created attachment 929190 [details] engine log
Verified with rhevm-3.5.0-0.10.master.el6ev.noarch. 1. install 2 hosts, at least 1 with pm. 2. stop network for host with pm. 3. all the messages as described in comment #1 were issued on audit log and appeared in ui as well as engine.log.
rhev 3.5.0 was released. closing.