Eli Mesika has submitted this change and it was merged. Change subject: core:Do not force fencing proxy to be ...(#876235) ...................................................................... core:Do not force fencing proxy to be ...(#876235) Do not force fencing proxy to be in UP status Currently when a host is non-responsive and has Power Management configured, we are looking for a proxy host in the same cluster to carry out the fencing commands that will actually reboot the problematic host. The algorithm of finding such a proxy was up to now to find the first host that is in UP status in the host DC. This patch modified the algorithm of proxy finding to 1) Look for a Host in the problematic Host DC which is UP 2) If 1) fails, try to use any other Host in the same DC as a proxy skipping Hosts is non-operational status with NETWORK_UNREACHABLE reason. This is done because there is no connection between the Host status and its ability to carry out proxy commands (which can be done if Host has network connectivity) although we can assume that a Host that is in UP status is connected to the network and its chance to succeed in carrying out the fencing operations is the best. Change-Id: I437e9b2bb0300f8d71cc8f0c50aaff1b253a63bb Signed-off-by: Eli Mesika <emesika(a)redhat.com&gt; --- M backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/FencingExecutor.java 1 file changed, 33 insertions(+), 3 deletions(-) Approvals: Eli Mesika: Verified; Looks good to me, approved -- To view, visit http://gerrit.ovirt.org/9251 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I437e9b2bb0300f8d71cc8f0c50aaff1b253a63bb Gerrit-PatchSet: 5 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Eli Mesika <emesika(a)redhat.com&gt; Gerrit-Reviewer: Eli Mesika <emesika(a)redhat.com&gt; Gerrit-Reviewer: Michael Kublin <mkublin(a)redhat.com&gt; Gerrit-Reviewer: Yair Zaslavsky <yzaslavs(a)redhat.com&gt;