OpenStack Compute (nova)

  1. Bug #1469179
  2. Comment #48

Comment 48 for bug 1469179

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

Reviewed: https://review.openstack.org/583715
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9344c1995a059675af7a8e9cf0de0502bef46c94
Submitter: Zuul
Branch: master

commit 9344c1995a059675af7a8e9cf0de0502bef46c94
Author: Matt Riedemann <email address hidden>
Date: Wed Jul 18 13:13:45 2018 -0400

    Heal RequestSpec.is_bfv for legacy instances during moves

    Change I9c2111f7377df65c1fc3c72323f85483b3295989 sets the
    RequestSpec.is_bfv flag for newly created instances so
    that scheduling (using placement) does not allocate DISK_GB
    resources for the Flavor's root_gb when booting from volume.

    RequestSpecs for old instances created before that change will
    not have the is_bfv field set, so this change adds a check for
    that in the various move operations (evacuate, unshelve, cold
    migrate and live migrate) and sets the RequestSpec.is_bfv flag
    accordingly.

    The related functional test is updated for the legacy cold
    migrate and heal scenario.

    Change-Id: I8e529ad4d707b2ad012328993892db83ce464c4b
    Closes-Bug: #1469179