yahoo-eng-team team mailing list archive

[OpenStack Infra <1819460@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/639608
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b096d9303acfea81ca56394cab681d2b2eed2d91
Submitter: Zuul
Branch:    master

commit b096d9303acfea81ca56394cab681d2b2eed2d91
Author: Balazs Gibizer <balazs.gibizer@xxxxxxxxxxxx>
Date:   Mon Mar 11 15:24:05 2019 +0100

    Handle placement error during re-schedule
    
    If claim_resources or _fill_provider_mapping calls fail due to placement
    error then the re-scheduling stops and the instance is not put into
    ERROR state.
    
    This patch adds proper exception handling to these cases.
    
    Change-Id: I78fc2312274471a7bd85a263de12cc5a0b19fd10
    Closes-Bug: #1819460


** Changed in: nova
       Status: In Progress => Fix Released

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

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