Bug 1389332
| Summary: | [el5][el6][el7-ppc64][el7-ppc64le] HA vms do not start after successful power-management. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Vinzenz Feenstra [evilissimo] <vfeenstr> |
| Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6.5 | CC: | dmoessne, fsun, gklein, hannsj_uhl, lsurette, melewis, mgoldboi, michal.skrivanek, mtessun, pstehlik, rbalakri, Rhev-m-bugs, srevivo, tjelinek, ykaul |
| Target Milestone: | ovirt-4.0.7 | Keywords: | Triaged, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, when virtual machines were stopped during a system shutdown or reboot they appeared to VDSM as if they had been shut down from within the guest operating system. This information was sent to the Red Hat Virtualization Manager and this meant that the Manager did not start highly available virtual machines on a different host because the Manager considered the the shut down of the virtual machines to be user-initiated. Now, the Red Hat Virtualization guest agent allows VDSM to detect that the virtual machine was shut down from within the system and this means that highly available virtual machines stopped during a system shutdown are restarted on a different host.
|
Story Points: | --- |
| Clone Of: | 1341106 | Environment: | |
| Last Closed: | 2017-03-16 15:28:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1341106 | ||
| Bug Blocks: | 1359843 | ||
|
Comment 2
Artyom
2016-11-21 14:41:35 UTC
(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 |