Submitter: Zuul
Branch:    master

commit c3a894b6af32ff8ddba728328bc7d4e1339b2964
Author: Hongbin Lu <>
Date:   Tue Feb 20 22:05:42 2018 +0000

    Skip placement on rebuild in same host
    If the instance is rebuilt with a different image in the same
    host, we don't need to call placement because there is no change
    in resource consumption.
    Change-Id: Ie252271ecfd38a0a1c61c26e323cc03869889f0a
    Closes-Bug: #1750623

** Changed in: nova
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  rebuild to same host with different image shouldn't check with

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  When doing a rebuild-to-same-host but with a different image, all we
  really want to do is ensure that the image properties for the new
  image are still valid for the current host.  Accordingly we need to go
  through the scheduler (to run the image-related filters) but we don't
  want to do anything related to resource consumption.

  Currently the scheduler will contact placement to get a pre-filtered
  list of compute nodes with sufficient free resources for the instance
  in question.  If the instance is on a compute node that is close to
  full, this may result in the current compute node being filtered out
  of the list, which will result in a noValidHost exception.

  Ideally, in the case where we are doing a rebuild-to-same-host we
  would simply retrieve the information for the current compute node
  from the DB instead of from placement, and then run the image-related
  scheduler filters.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to