Bug 1526024
| Summary: | The VM configured with resume_behavior='AUTO_RESUME' is not resumed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> | ||||
| Component: | BLL.Virt | Assignee: | Michal Skrivanek <michal.skrivanek> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.2.0 | CC: | bugs, tjelinek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-15 07:30:36 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 1526025 *** |
Created attachment 1368076 [details] In the attached engine.log please see the scenario from line 3911. Description of problem: There is a scenario where VM with resume_behavior='AUTO_RESUME' configuration is not resumed. please see steps to reproduce Version-Release number of selected component (if applicable): rhvm-4.2.0-0.6.el7.noarch How reproducible: 100 % Steps to Reproduce: 1. Have running HA VM with Resume Behavior = 'AutoResume'. Block the storage -> VM Paused since I/O error. 2. while this state try to run the VM. As result sometimes the VM just stay in the same I/O Pause. And sometimes the I/O error Pause is changed to Pause. it doesn't affect the next behavior - the same in both cases. In the attached engine.log please see the scenario from line 3911. 3. unblock the storage after while => the VM remains Paused instead of being Resumed. Actual results: VM remains Paused despite of the AutoResume configuration. Expected results: VM must be Auto Resumed Additional info:Trying to manually start the VM after this scenario brings firstly error: Launching VM Failed, and then it is started.