Bug 1381598

Are you completely sure that you copied the relevant disks of the template to the destination storage domain? How did you do that? Take into account that just copying the template won't work, you have to copy each disk, so they will effectively have the same id. To check in what storage domains are the disks available you can do something like this:

  for disk in template.disks.list():
      for sd in disk.get_storage_domains().get_storage_domain():
          sd = api.storagedomains.get(id=sd.get_id())
          print('%s %s' % (disk.get_id(), sd.get_name()))

That will print something like this:

  12db9d50-00a9-4caa-a519-5a9ffd39c046 mydata
  12db9d50-00a9-4caa-a519-5a9ffd39c046 yourdata

In order to correctly copy the template disks you can also use the API:

  for disk in template.disks.list():
      disk.copy(
         action=params.Action(
             storage_domain=params.StorageDomain(id=sd.get_id()),
         ),
     )

Note also that in your example you are sending the complete representation of the storage domain, when only the id is needed:

  action = params.Action(storage_domain=blocksd, async=False)

Try to do the following instead:

  action = params.Action(
      storage_domain=params.StorageDomain(id=blocksd.get_id()),
      async=False,
  )

Created attachment 1207258 [details]
Screenshot of the template

As per your description, I would say it's copied correctly. I'm attaching a screenshot of the template view to confirm, however, the template has only one disk and I did the following to copy it to the other datastore:

1) Choose the 'Templates' tab
2) Select the template of interest.
3) Click on the 'Disks' subtab.
4) Choose the origin datastore, and select 'Copy'.
5) Choose the destination datastore and click on 'OK'.

In the screenshot, iscsiceph01 is the origin and ceph02 the destination backends respectively.

I also run the code you included and the result is:

(venv)# python test.py 
77c7e959-3486-413e-af17-d509a41249fc iscsiceph01
77c7e959-3486-413e-af17-d509a41249fc ceph02

Also note that, as I initially said, I can do that operation from within the webadmin. It's just the Python-SDK that fails.

Thanks for the detailed answer Nicolas, I think you are copying it correctly. I did test this with two NFS storage domains, and it worked correctly. It may be related to the fact that you are using iSCSI and Ceph.

Allon, can you take a look, please?

Note that this works when VMs are not inside a VmPool. I migrated lots of singular VMs without any issue - it's just VmPool machines that have this problem.

Fred, can you take a look at this please?

Nicolas, are you working with cinder ?

No, all of them are iSCSI based datastores, some of them "pure" iSCSI and some of them acting as a gateway to a Ceph backend, but even those have copies of the templates.

I tried running the script again and now it works with no issues.

The only change we've done recently is upgrading from 4.0.3 to 4.0.4, however I'm unable to find some fix in the CHANGELOG referencing templates or vmpools that could affect (at least not directly). I'm 100% sure the migration script was not changed.

Closing for now, as neither side can reproduce. If this occurs again, plesae feel free to reopen!