[Yahoo-eng-team] [Bug 1748697] Re: Cold migration fails when the filter only returns the host where the vm is located and the vm status is set to ERROR

Reviewed: https://review.opendev.org/695220 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4921e822e73383af0c8da4c5e3acfaa021eafe68 Submitter: Zuul Branch:master commit 4921e822e73383af0c8da4c5e3acfaa021eafe68 Author: Matt Riedemann Date: Wed Nov 20 10:27:18 2019

[Yahoo-eng-team] [Bug 1748697] Re: Cold migration fails when the filter only returns the host where the vm is located and the vm status is set to ERROR

Hi,sylvain-bauza, in some cases instance will be set to ERROR state when migrate failed (such as UnableToMigrateToSelf),we can simply return the error to upper layer (operater or user) to avoid make user run reset to restore instance status since no changes to guest at all. ** Changed in: nova

[Yahoo-eng-team] [Bug 1748697] Re: Cold migration fails when the filter only returns the host where the vm is located and the vm status is set to ERROR

Some Nova virt drivers support migrating to the same host (VMWare at least). That's why it's not meaningless to accept migrating to a same host. Anyway, given your concern would be asking to have a different behaviour for cold-migrating, it would need a new API microversion hence a new spec and a