yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

I'll be backporting the non-fill provider mapping part of this to rocky
and queens since the code fix and functional tests related to bug
1837955 rely on changes from the series that fixed this bug.

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

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

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

Title:
  instance stuck in BUILD state due to unhandled exceptions in conductor

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  Confirmed
Status in OpenStack Compute (nova) rocky series:
  Confirmed
Status in OpenStack Compute (nova) stein series:
  Fix Committed

Bug description:
  There are two calls[1][2] during ConductorTaskManager.build_instances,
  used during re-schedule, that could potentially raise exceptions which
  leads to that the instance is stuck in BUILD state instead of going to
  ERROR state.


  [1] https://github.com/openstack/nova/blob/892ead1438abc9a8a876209343e6a85c80f0059f/nova/conductor/manager.py#L670
  [2] https://github.com/openstack/nova/blob/892ead1438abc9a8a876209343e6a85c80f0059f/nova/conductor/manager.py#L679

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