IMPORT : Importing VM with multiple disk BUG

Latest response

RHEV 3.1.0-50

Hit this rather horrible bug at the weekend whist migrating VM's between RHEV platforms using the Export/Imort method.

When using the Export storage domain to import a VM with multiple disks assigned, it reports the import of the VM as complete upon the successfull import of EACH disk. This is wrong. It should only report as complete upon the successfull import of the final disk.

More importantly, the VM is unlocked after the import of only the first disk allowing the user to make changes to the VM and potentially start it or make changes before the remaining disks have been imported. This is very dangerous and can corrupt the VM causing all manor of issues.

A high pri support call has been raised.

Responses

> More importantly, the VM is unlocked after the import of only the first disk allowing the user to make changes to the VM and potentially start it or make changes before the remaining disks have been imported. This is very dangerous and can corrupt the VM causing all manor of issues.

I am guessing, not verified it personally. VMs and Disks are managed separately in RHEV_3.1. There are separate locks for vms and disks. To start a vm, only the boot disk is enough. So once we finish importing it, we unlock the vm. I believe disks in locked status (second disk being imported) will not be attached to the vm if you start it at this time. Does it still sound dangerous? I believe we cannot corrupt a disk which is not attached in anyway.

I was wrong in my guess. This has been escalated as a bug to engineering and a future release should have a fix for this issue.

Some details at http://gerrit.ovirt.org/#/c/11326/