Hyper-V live-migration rollback leaves destination node in inconsistent state

[Timofey Durakov]

Roll-back of destination node in case of live-migration failure depends on block-migrate flag that passed by operator. So it's possible to leave destination node in inconsistent state by passing block-migrate flag, over api.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/216329
Reason: This code hasn't been updated in a long time, and is in merge conflict. I am going to abandon this review, but feel free to restore it if you're still working on this.

[Sean Dague (sdague)]

There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments.

[Claudiu Belu (cbelu)]

Marked as incomplete, because the bug report does not contain enough information in order to determine and reproduce the issue.

What flags did you pass to the live-migration? Were the hosts on shared storage, or local storage? What is the reason for the rollback? What do you mean by "leaving the destination node in an inconsistent state"?

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

[Claudiu Belu (cbelu)]

Addressed by: https://review.openstack.org/#/c/478943/