Red Hat Bugzilla – Bug 1368202
HA VMs are not restarted on different host if NonResponsive host is off and start action failed
Last modified: 2018-05-02 09:23:15 EDT
+++ This bug was initially created as a clone of Bug #1367557 +++ Description of problem: HA VMs are not restarted on different host(s) if NonResponsive host is off (detected by successful power management status action) and start power management action failed Version-Release number of selected component (if applicable): 3.0 and later How reproducible: 100% Steps to Reproduce: 1. Create 2 or more hosts cluster with power management properly configured 2. Run HA VMs on host1 and make this host non responsive by turning the power off 3. Make sure that power management status of host1 can be properly detected, but power management start action failed 4. Check that fence of host1 failed and HA VMs are not restarted on different hosts although we detect that host1 is turned off using power management Actual results: HA VMs are not restarted on different host even though host1 is powered off Expected results: HA VMs are restarted on different hosts Additional info:
We would also need this fix to be backported to RHEV 3.6 as well.
Moving to 4.0.4 to sync with upstream bug. Once it's merged to 4.0.z, we can clone this into 3.6.z
Moving to MODIFIED to sync with upstream bug
Verify with: rhevm-4.0.4.2-0.1.el7ev.noarch Hosts with PM: OS Version:RHEL - 7.2 - 9.el7 OS Description:Red Hat Enterprise Linux Server 7.2 (Maipo) Kernel Version:3.10.0 - 327.28.3.el7.x86_64 KVM Version:2.3.0 - 31.el7_2.21 LIBVIRT Version:libvirt-1.2.17-13.el7_2.5 VDSM Version:vdsm-4.18.13-1.el7ev Steps: 1. Create 2 hosts in cluster with power management properly configured 2. Run HA 2 VMs and 1 none HA VM on host1 3. Turn power off host_1 from power management and setup host not to power up(from remote PM iLO4 in this case) 4. Check HA VMs are started on host_2 Results: HA VMs run on host_2 - PASS
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-1967.html