cloudstack: migrateVolume does not copy the template

When a volume is copied to another storage pool, if the template does not exist in the destination storage pool yet, it should be copied. The API migrateVirtualMachineWithVolume already does it; however, when migrating the volume with migrateVolume (VM stopped), the template is not copied, which causes inconsistencies in the database and primary storage systems.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 18 (18 by maintainers)

Most upvoted comments

@rohityadavcloud @GutoVeronezi I have tested with local storage as well shared storage. both work. The migrateVolume will firstly copy the image to secondary storage (full clone) and then copy to another primary storage. It should not be a bug. therefore I have removed the label ‘type:bug’ The whole process can be improved of course.

Thanks for the tests, @weizhouapache.

@GutoVeronezi please feel free to improve it.

weizhouapache on Jan 30, 2023