Bug 949281
| Summary: | Hibernate VM was started for a VM that has already Hibernate VM run for. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yair Zaslavsky <yzaslavs> | ||||||
| Component: | ovirt-engine | Assignee: | Arik <ahadas> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Tareq Alayan <talayan> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 3.2.0 | CC: | acathrow, ahadas, iheim, jkt, lpeer, michal.skrivanek, oourfali, Rhev-m-bugs, yeylon | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.3.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | virt | ||||||||
| Fixed In Version: | is1 | Doc Type: | Enhancement | ||||||
| Doc Text: |
This update introduces a new PrepareForHibernation virtual machine status, which denotes that a virtual machine is about to hibernate but VDSM had not yet saved its memory state. The status changes to SavingState when the 'hibernate' verb is called in VDSM and VDSM reports back that it has started migrating to the file.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-01-21 17:16:59 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 782526, 947069, 1019461 | ||||||||
| Attachments: |
|
||||||||
Created attachment 732336 [details]
hibernate vm engine log
I would suggest to consider to override the compensate method for this command , and in case there are existing tasks, not rollback the saving state. is it possible to postpone till 3.3? The fix is getting too complicated and risky http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=677e6a4eb5129cbb94a99ba7780dfd8ca7150739 http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=594b23fdf73823418127c5c0b00bec6149870d9f http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=17e25bf5500d9988eaf4efa34fe581449809a830 http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=0d3ba62ae9ae2e3fabe3421a1b18cedd6ff17427 This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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. http://rhn.redhat.com/errata/RHSA-2014-0038.html |
Created attachment 732335 [details] log from customer. Description of problem: In case Hibernate VM is run on a VM, and engine restarts, It is possible to run Hibernate VM again, as the VM is not in saving state. This happens due to the compensation mechanism which rolls back the vm status from SAVING to UP. At endAction there is a check, and if the VM is not in saving state (the first hibernate command might have already ended) the Hibernate VDSM verb is not sent (so this area is covered, but It would be also nice to block the CreateImage tasks). Version-Release number of selected component (if applicable): How reproducible: As explained above Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: