yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: rebuild scheduler

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1750623

Title:
  rebuild to same host with different image shouldn't check with
  placement

Status in OpenStack Compute (nova):
  New

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:
https://bugs.launchpad.net/nova/+bug/1750623/+subscriptions