Migration task cancelled but still occurring?
-
I started to migrate one of my VMs from one host to another along with moving from shared to local storage on that host. After a few minutes I decided I didn't want to do that and I cancelled the migration task. I no longer see anything in the task view but I'm still seeing network and disk traffic that indicates that the migration is occurring.
How can I make sure the migration is truly cancelled? Do I need to do any manual SR cleanup?
-
I'm not sure how cancellation of a migration tasks works, but maybe it has to finish the migration and then delete the VDI that it moved? Not sure if it can cancel and clean it up in the middle of a migrate.
How big is the VM? If it's not going to take crazy long to migrate then probably worth just waiting until you don't see that network traffic anymore, and then check if you see the VDI in both places or not; and probably double check the location of the VMs VDI afterwards too.
-
@CJ Restart the toolstack to clear out the phantom migration.
-
Well, if I understand right, the concern here isn't that a migration task shows but nothing is happening, I think it's the other way around. No migration task is shown, but network stats show a lot of bandwidth being used.
Correct me if I am wrong @CJ
-
@planedrop Yes, that is correct. The traffic eventually stopped. I just checked and there was an orphaned VDI on the local storage.
I'm assuming that the cancellation just stopped the VM from migrating but the VDI was still copied over in full, which seems a waste.
-
@CJ Yes, this sounds right, pretty sure I've come across it too actually. Not sure what the best solution is though, it makes logical sense to finish the VDI migrate, then just not migrate the VM itself, but would be nice if it automatically removed that VDI afterwards too rather than leaving it orphaned.
-
@planedrop Why does it make sense to keep copying a VDI if there's no migration? It's just wasting resources.
-
@CJ It may be easier to ensure reliability and prevent other possible issues from happening. I'm not an expert when it comes to the underlying code, but I would take an orphaned VDI over say some form of corruption or something like that.
I'm guessing a little if I'm being honest, but cancelling it mid transfer might break some things, could leave a partial VDI that is locked for example, etc...
