yahoo-eng-team team mailing list archive

[Russell Bryant <1329559@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => juno-2

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

Title:
  Cannot delete an instance that failed a previous delete

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Currently we have a situation where if an instance fails to delete,
  instead of having its state reverted, like we do in most places we set
  it to error,deleting. This was intentionally done in
  https://review.openstack.org/#/c/58829/ . We also intentionally ignore
  duplicate requests to delete an instance if its already being deleted
  (https://review.openstack.org/#/c/55444/). The combination of these two
  things means that if an instance fails to delete for some reason a
  tenant is unable to delete that instance.

  It turns out this is really bad because instances in deleting state
  count against quota, so the tenant slowly looses usable quota.

  To fix this, allow duplicate delete calls to go through if the instance
  is in error state.

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