yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

** Also affects: nova/newton
   Importance: Undecided
       Status: New

** Tags added: cells

-- 
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/1628530

Title:
  Rescheduling an instance leaves it in a scheduling state and never
  succeeds

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) newton series:
  New

Bug description:
  mamandle reported to me on IRC that commit
  https://github.com/openstack/nova/commit/f577f650c7ca9d8dd66eaec919e4805c09d16f6d
  broke reschedules. Looking at it I see the issue which is that on a
  reschedule there is no BuildRequest object in the db so the logic that
  checks for that will stop the build attempt from progressing further.
  That code is in place to handle the case where a delete happens during
  the build process but did not properly account for reschedules.

  In the case of a reschedule instance.launched_on will be set so we can
  bypass looking for the BuildRequest object in that case. Since the
  BuildRequest was deleted during the first scheduling pass it's okay to
  do that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1628530/+subscriptions