Comment 3 for bug 1561357

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/297387
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=446d15568e00a483d909dc5c565d70baf29179ad
Submitter: Jenkins
Branch: master

commit 446d15568e00a483d909dc5c565d70baf29179ad
Author: Sylvain Bauza <email address hidden>
Date: Thu Mar 24 23:07:54 2016 +0100

    Stop providing force_hosts to the scheduler for move ops

    Since now we provide the original RequestSpec for move operations (unshelve,
    live-migrate and evacuate), it can also provide the original force_hosts/nodes
    to the scheduler.
    In that case, it means that if an admin was asking to boot an instance forcing
    to an host, a later move operation could then give again the forced value and
    then wouldn't permit to get a different destination which is an issue.

    TBH, that is not a problem for live-migrate and evacuate that do provide an
    optional host value (which bypasses then the scheduler) but since unshelve
    is not having this optional value, it would mean that we could only unshelve
    an forced instance to the same host.

    Change-Id: I03c22ff757d0ee1da9d69fa48cc4bdd036e6b13f
    Closes-Bug: #1561357