Description of problem: When a host is manually fenced, HA VMs that are stopped on that host aren't restarted automatically Version-Release number of selected component (if applicable): 3.2 How reproducible: Very Steps to Reproduce: 1. Start HA VMs on hypervisor 2. Manually fence the hypervisor Actual results: HA VMs are not restarted Expected results: HA VMs restarted Additional info: This is happening in 3.1 and 3.2
Was fencing set up on the host? In between step 1 and step 2 did the host get powered down or lose network connectivity ? Can we get logs attached to the BZ or linked? thanks.
Description of problem: If a host containing a guest configured as HA goes down and fencing fails, after host comes back and rejoins the cluster guest is not restarted. Version-Release number of selected component (if applicable): rhevm-3.2.0-11.37.el6ev How reproducible: Always. Steps to Reproduce: 1. Configure a guest to be a HA guest (HA option enabled). 2. Disable fencing on one RHEV host (e.g. change fencing device password so fencing attempts fail). 3. Kill 'vdsmd' on host where HA guest runs. 4. Wait for fencing attempts to fail, after about 3 minutes RHEV-M will report host as "Non Responsive". 5. Manually stop HA guest (e.g. ssh ha-vm "sudo poweroff"). 6. Manually reboot host. 7. Wait for host to boot up and rejoin RHEV cluster. Actual results: HA guest is not restarted after host rejoins the cluster. Expected results: HA guest is restarted after host rejoins the cluster. Additional info: Will follow up with sosreports and LogCollector details.
According to DB analysis this report may not be an issue. If anyone is able to reproduce with HA VMs, please reopen.