Red Hat Bugzilla – Bug 1294350
pre starting vms in pool fail with stateless snapshot stuck in locked state
Last modified: 2016-05-24 12:13:09 EDT
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):
Steps to Reproduce:
1. Create vm pool with some vms lets say 3.
2. Edit pool and set prestarted vms to x <=3.
after VmPoolMonitorIntervalInMinutes vm are trying to start but fail leaving the stateless snapshot locked.
prestarted vms start successfully with a working stateless snapshot.
might be due to the fix for the following bz:
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.
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.
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.
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.
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.
(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.
*** Bug 1294349 has been marked as a duplicate of this bug. ***