Red Hat Bugzilla – Bug 1313703
Unable to create a vm from template imported from Glance
Last modified: 2016-03-03 09:58:23 EST
Description of problem:
create vm from template imported from Glance fails with the below error (in actual results)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add dc
2. add cluster
3. add hosts
4. add sds
5. import image from glance as template
6. get status ok on imported disk
6. copy the template to all sds
7. create a vm from this template
00:24:31.398 Reason: Conflict
00:24:31.398 Detail: [Cannot add VM. Disk golden_mixed_virtio_template is being moved or copied.]
we should be able to create a vm from this tempalte
will attach the logs from the last execution soon
Created attachment 1132196 [details]
Created attachment 1132197 [details]
vdsm logs from all hosts
This issue exists in the following commits of engine and vdsm:
Engine: ded51e3bcac65f194ef2c80818677891fa12d30c ovirt-engine-3.6 branch
core: Unit tests for VmDevicesMonitoring
VDSM: c2b9e0075880a175ba2b7a3c58d15a00831c73be ovirt-3.6.3 branch
oVirt 3.6.3 refresh (storage fix)
Essential we use latest vdsm-4.17.23-0.el7ev.noarch.rpm from brew
I will try to track previous versions to find when the problem started to appear and update. However it may be not easy as previously it was not consistently reproducible.
Fred, as this week's qa contact can you take a look please?
(In reply to Nelly Credi from comment #0)
> Actual results:
> Status: 409
> 00:24:31.398 Reason: Conflict
> 00:24:31.398 Detail: [Cannot add VM. Disk golden_mixed_virtio_template is
> being moved or copied.]
It looks like you try to create a vm before copying the template finished.
How do you verify that the copy operation finished before trying to create a vm?
copying the template is a sync action, so we just wait for it to finish
Please also keep in mind that this is working well in 3.6.3
(In reply to Nelly Credi from comment #6)
> copying the template is a sync action, so we just wait for it to finish
Can you explain how do you perform the copy template? Python SDK? REST API?
> Please also keep in mind that this is working well in 3.6.3
Can you provide engine and vdsm logs from "good" 3.6.3 run?
Created attachment 1132688 [details]
Good execution - engine logs
We are using REST
Created attachment 1132689 [details]
good execution - hosts log
By looking at the REST log in , I can see that the disk is in "locked" state right before the VM creation.
2016-03-02 20:31:51,821 ---> get on the template, disk is locked
2016-03-02 20:31:52,018 ---> create VM with failure
So it could be some timing/logic issue in the test.
The disk status should be checked to be OK before creating the VM