Hyper-V: properly handle shared storage during migrations
In case of migrations, we attempt to move the instance files without
checking whether shared storage is used. Note that the block_migration
flag is ignored.
After a live migration is performed, we always try to delete the
instance files. Also, if the migration fails, the destination node is
not cleaned up, as the HyperVLiveMigrateData object is not used at the
moment.
Reviewed: https:/ /review. openstack. org/335114 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=5ee7f3b30ca e5f122ab85d6422 a7d9dfd12ff9ab
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5ee7f3b30cae5f1 22ab85d6422a7d9 dfd12ff9ab
Author: Lucian Petrut <email address hidden>
Date: Thu Jun 16 11:41:20 2016 +0300
Hyper-V: properly handle shared storage during migrations
In case of migrations, we attempt to move the instance files without
checking whether shared storage is used. Note that the block_migration
flag is ignored.
After a live migration is performed, we always try to delete the teData object is not used at the
instance files. Also, if the migration fails, the destination node is
not cleaned up, as the HyperVLiveMigra
moment.
This change addresses those issues.
Partial-Bug: #1565895
Change-Id: I0ac0a2d2e7a877 1024a486dd5931b d05b1ecd074