Verified on: rhevm-4.0.6-0.1.el7ev.noarch ovirt-guest-agent-common-1.0.13-2.el6.noarch Checked scenario: 1) Power off HA VM from the engine - VM stay in stated DOWN 2) Power off HA VM from the guest OS - VM stay in stated DOWN 3) Power off host where HA VM runs via engine power management action - VM starts on the other host (straight forward after action) 4) Power off host where HA VM runs via host OS - VM starts on the other host (need to wait until engine will execute power management action)
(In reply to Artyom from comment #2) > Verified on: > rhevm-4.0.6-0.1.el7ev.noarch > ovirt-guest-agent-common-1.0.13-2.el6.noarch > > Checked scenario: > 1) Power off HA VM from the engine - VM stay in stated DOWN > 2) Power off HA VM from the guest OS - VM stay in stated DOWN > 3) Power off host where HA VM runs via engine power management action - VM > starts on the other host (straight forward after action) > 4) Power off host where HA VM runs via host OS - VM starts on the other host > (need to wait until engine will execute power management action) This was moved to ON_QA incorrectly by the rhev-integ, and then it was verified incorrectly using a 4.1 version of guest agent, but the point was to test a 4.0 backport. Moving back to MODIFIED, it needs to be built downstream
I move bug to assigned until we will have build for 4.0.7
Verified on: Red Hat Enterprise Linux Server release 6.8 Beta (Santiago) rhevm-guest-agent-common-1.0.12-4.el6ev.noarch.rpm Red Hat Enterprise Linux Server release 5.11 (Tikanga) rhevm-guest-agent-1.0.12-6.el5ev.noarch.rpm Checked scenario: 1) Power off the HA VM from the engine - the engine does not start the VM 2) Power off the HA VM from the guest OS - the engine does not start the VM 3) Power off the host where the HA VM runs via the engine power management action - the engine starts the on the other host 4) Power off the host where HA VM runs via host OS - the engine starts the on the other host
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/RHBA-2017-0538.html