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 => juno-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/1361097

Title:
  Compute exception text never present when max sched attempt reached

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When scheduling VMs and the retry logic kicks in, the failed compute
  exception text is saved to be displayed for triaging purposes in the
  conductor/scheduler logs.  When the conductor tries to display the
  exception text when the maximum scheduling attempts have been reached,
  the exception always shows 'None' for the exception text.

  Snippet from scheduler_utils.py...

   msg = (_('Exceeded max scheduling attempts %(max_attempts)d '
  'for instance %(instance_uuid)s. '
  'Last exception: %(exc)s.')
  % {'max_attempts': max_attempts,
  'instance_uuid': instance_uuid,
  'exc': exc})

  That is, 'exc' is erroneously ALWAYS None in this case.

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