yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1626702@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

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

Title:
  Instances deletes should be asynchronous with host availability

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description: When a host goes down and instances on that host are
  deleted while the host is down, this request should be tracked in the
  database so that when the host comes back up it can scrub the delete
  request against the status of the active instance and delete it if
  necessary. The overall goal is for the delete to be processed so that
  any attached volumes return to an available state instead of being
  left in an in-use state. (attached to a non-existent instance)

  This is being experienced while using Cloud Foundry. When the host
  goes down, Bosh attempts to re-create the instance along with
  associating any previous known volumes.

  This has been tested on the following tag:
  10.1.18

  If this was not an issue, I would expect the delete request to go
  through while the host was down and the system itself would clean up
  the mess once the host comes back online freeing up the volume for use
  immediately.

  (This is going to be tested in Liberty as well and further notes will
  be attached to the bug report)

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