Bug 1526024 - The VM configured with resume_behavior='AUTO_RESUME' is not resumed
Summary: The VM configured with resume_behavior='AUTO_RESUME' is not resumed
Keywords:
Status: CLOSED DUPLICATE of bug 1526025
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-14 16:11 UTC by Polina
Modified: 2017-12-15 07:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-15 07:30:36 UTC
oVirt Team: Virt
Embargoed:


Attachments (Terms of Use)
In the attached engine.log please see the scenario from line 3911. (16.50 MB, application/x-gzip)
2017-12-14 16:11 UTC, Polina
no flags Details

Description Polina 2017-12-14 16:11:55 UTC
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.

Comment 1 Tomas Jelinek 2017-12-15 07:30:36 UTC

*** This bug has been marked as a duplicate of bug 1526025 ***


Note You need to log in before you can comment on or make changes to this bug.