Bug 1294350 - pre starting vms in pool fail with stateless snapshot stuck in locked state
Summary: pre starting vms in pool fail with stateless snapshot stuck in locked state
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-3.6.3
: 3.6.3
Assignee: Michal Skrivanek
QA Contact: sefi litmanovich
URL:
Whiteboard:
: 1294349 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-27 12:28 UTC by sefi litmanovich
Modified: 2016-05-24 16:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:05:33 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-3.6.z+
rule-engine: blocker+
rule-engine: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1339308 0 high CLOSED stateless vms fail to start - stateless snapshot is locked forever 2021-02-22 00:41:40 UTC

Internal Links: 1339308

Description sefi litmanovich 2015-12-27 12:28:03 UTC
Description of problem:

After creating vm pool with X vms I edit the pool and define e.g. 2 prestarted vms.
after the defined VmPoolMonitorIntervalInMinutes (this happened with values set to 1) engine attempts to start 2 vms from the pool but fails leaving the 2 vms down with 'stateless snapshot' stuck in locked state.
After another VmPoolMonitorIntervalInMinutes engine attempts to start 2 new vms and same thing happens until pool has run out of vms.

The same thing happens when trying to start a stateless vm.

Version-Release number of selected component (if applicable):
rhevm-3.6.2-0.1.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Create vm pool with some vms lets say 3.
2. Edit pool and set prestarted vms to x <=3.


Actual results:

after VmPoolMonitorIntervalInMinutes vm are trying to start but fail leaving the stateless snapshot locked.

Expected results:

prestarted vms start successfully with a working stateless snapshot.

Additional info:

might be due to the fix for the following bz: 
https://bugzilla.redhat.com/show_bug.cgi?id=1287771

Comment 2 Red Hat Bugzilla Rules Engine 2015-12-27 13:44:32 UTC
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.

Comment 3 Red Hat Bugzilla Rules Engine 2016-01-03 09:58:48 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 4 Red Hat Bugzilla Rules Engine 2016-01-28 12:16:00 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 5 Red Hat Bugzilla Rules Engine 2016-01-28 12:24:51 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 6 Red Hat Bugzilla Rules Engine 2016-01-28 12:28:58 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 7 Michal Skrivanek 2016-01-28 14:48:26 UTC
I wonder whether you find entries since comment #2 onwards useful. 
I find it confusing, useless and a waste of time for anyone who has to deal with this bug.
Please disable the bot, and set up whines instead.

Comment 8 sefi litmanovich 2016-01-28 16:34:51 UTC
Verified with rhevm-3.6.3-0.1.el6.noarch.

checked both stateless vm and prestarted pool vms (which is the same), snapshot created successfully and delted when shutting vm down as expected.

Comment 9 Yaniv Lavi 2016-01-28 20:28:32 UTC
(In reply to Michal Skrivanek from comment #7)
> I wonder whether you find entries since comment #2 onwards useful. 
> I find it confusing, useless and a waste of time for anyone who has to deal
> with this bug.
> Please disable the bot, and set up whines instead.

The person doing the build need to set target release. you can CI to not move bugs unless they have target release.

Comment 10 sefi litmanovich 2016-02-04 15:27:21 UTC
*** Bug 1294349 has been marked as a duplicate of this bug. ***


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