Description of problem: When a VM is live migrated to another host and the engine tries to cancel the operation because of some connectivity issues. The command CancelMigrateVDSCommand can failed and the VM remain in the migration state. Version-Release number of selected component (if applicable): 3.1.5 How reproducible: Not 100% sure Steps to Reproduce: I am not sure, but it should be possible to start the migration and then force some connectivity issue and make the cancle operation to fail. Actual results: VM is in "Migration to" state Expected results: VM is down or UP depends on the status of the VM. Additional info:
it's hard to tell anything without vdsm logs, but it seems the VM didn't exist on source when hitting cancel (2013-06-14 17:40:21,017, cacnel failed with "Migration not in progress"). It may have finished the migration right before that - the status as shown in GUI may have been obfuscated by not responding host. Can you check that and/or supply vdsm logs along with engine?
ok...