yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => kilo-3

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

Title:
  Rescheduling loses reasons

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  In nova.compute.manager when an instance is rescheduled (for whatever
  reason) the exception that caused said rescheduling is only logged,
  and not shown to the user in any fashion. In the extreme case this can
  cause the user to have no idea what happened when rescheduling finally
  fails.

  For example:

  Say the following happens, on schedule instance 1, on hypervisor A it errors with error X then rescheduled to hypervisor B, which
  errors with error Y, then next can't reschedule due to no more hypervisors being able to be scheduled to (aka no more compute nodes), then you basically get an error that says no more instances to schedule on (which is not connected to the original error in any fashion).

  Likely there needs to be a record of the rescheduling exceptions, or
  rescheduling needs to be rethought, where a orchestration unit can
  perform this rescheduling and be more aware of the rescheduling
  attempts (and there success and failures).

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