yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #79444
[Bug 1819460] Re: instance stuck in BUILD state due to unhandled exceptions in conductor
Actually ignore comment 15, claim_resources didn't raise
AllocationUpdateFailed until Stein:
https://github.com/openstack/nova/commit/37301f2f278a3702369eec957402e36d53068973
So the bug doesn't apply to Rocky or Queens.
** No longer affects: nova/rocky
** No longer affects: nova/queens
--
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) 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
References