yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1248563] Re: Instance deletion is prevented when another component locks up

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Russell Bryant <1248563@xxxxxxxxxxxxxxxxxx>
Date: Wed, 23 Jul 2014 14:51:58 -0000
Reply-to: Bug 1248563 <1248563@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** 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/1248563

Title:
  Instance deletion is prevented when another component locks up

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Instance deletion can be delayed (even effectively prevented) if one
  of the components locks up. This is due to other operations holding
  the lock on the uuid, which is also needed by terminate_instances. A
  side effect of that is that the delete messages start queueing up,
  preventing other operations on the same compute manager.

  This issue has been discussed on mailing list, starting with post
  http://lists.openstack.org/pipermail/openstack-
  dev/2013-October/017454.html

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