Red Hat Bugzilla – Bug 994860
VM image stays locked when creating template and closing engine
Last modified: 2015-09-22 09:09 EDT
Created attachment 784241 [details]
oVirt engine log
Description of problem:
I tried to make a template out of a VM, then closed the engine for the night. Turned it back on this morning, and found that VM status is still "Image Locked". The template appears in the templates tab, but can't be used to create a new VM from.
Version-Release number of selected component (if applicable):
oVirt 3.3 master branch.
Haven't tried more than once, steps below.
Steps to Reproduce:
1. Create VM.
2. Create template from VM.
3. Shut down engine for 12 hours.
Image stays locked, VM can't be run and new VMs can't be created from the template.
Image surely shouldn't be locked anymore after 12 hours, VM and template should be usable.
Attached engine log, please disregard the cluttering errors about the decryption of the engine admin password.
the locking of template creation was removed, so the template is indeed created right away and then the image creation lock&release is a separate operation. Moving to storage
This is probably due to the recent changes in async task manager.
Liron, please take a look?
Michal, the issue is related to the parameters serialization and also relates to change http://gerrit.ovirt.org/#/c/14584/
the master vm isn't being serialized, thus NPE is caused when attempting to use parameterMasterVm.getDefaultDisplayType() @ line 110.
moving back to virt, we need to see if the bug is general (master vm isn't being serialized) or we are fine with it not being serialized but shouldn't access it's properties when it's null.
(In reply to Liron Aravot from comment #3)
> Michal, the issue is related to the parameters serialization and also
> relates to change http://gerrit.ovirt.org/#/c/14584/
> the master vm isn't being serialized, thus NPE is caused when attempting to
> use parameterMasterVm.getDefaultDisplayType() @ line 110.
right, master vm is not serialized and used in ctor without a null check.
in order to verify I need verification steps,
Reproduction steps will take too long and I am almost sure we shouldn't wait 12 hours.
can you please share better steps?
(In reply to Aharon Canan from comment #5)
> in order to verify I need verification steps,
> Reproduction steps will take too long and I am almost sure we shouldn't wait
> 12 hours.
> can you please share better steps?
yes, just restart engine while creating a template (vm and templated in locked status),
if you have large disk (>3gb preallocated) it should be enough.
no need to wait
Following comment #6, verified using is12
1. Create VM
2. Create template
3. while image lock restart engine
4. after engine back start the VM and create new VM from template you created and run it as well.
Closing - RHEV 3.3 Released