Created attachment 960705[details]
image+logs
Description of problem:
After exporting VM based on a template, the VM gets blocked with a status showing image is locked
Version-Release number of selected component (if applicable):
3.5 vt11
How reproducible:
100%
Steps to Reproduce:
1. Create a VM based on a template
2. Create a Snapshot of the VM
3. Export the VM to an export domain
Actual results:
VM gets blocked with a status showing image is locked
Expected results:
The export process should succeed
Additional info:
Attach screenshot
This occurs not on every export operation, only when the export ended and the getImageInfo in the end command part is failing (most likely on communication error with VDSM)
This isn't a blocker - it happens only in a very rare negative case (copying all the disks succeeds and only then vdsm fails just before the last getImageInfo is sent). Additionally, it's been there since 3.3, at least.
It definitely needs fixing, and we'll treat it as an exception, but it's not blocker-worthy.
Patch posted, just to clarify - this occurs in the extremely rare scenario where the import of the images succeeded with copy collapse and connection problems to the host are occurring right after the export task completed and before the OVF image on the export domain is getting updated with the new info (since the snapshots have been collapsed)
Created attachment 960705 [details] image+logs Description of problem: After exporting VM based on a template, the VM gets blocked with a status showing image is locked Version-Release number of selected component (if applicable): 3.5 vt11 How reproducible: 100% Steps to Reproduce: 1. Create a VM based on a template 2. Create a Snapshot of the VM 3. Export the VM to an export domain Actual results: VM gets blocked with a status showing image is locked Expected results: The export process should succeed Additional info: Attach screenshot