yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

needs to be verified against folsom

** Changed in: nova
    Milestone: grizzly-rc1 => None

** Also affects: nova/folsom
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: Triaged => Invalid

** Changed in: nova/folsom
       Status: New => Triaged

** Changed in: nova/folsom
   Importance: Undecided => High

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

Title:
  deleting instance while volume is being attached leaves volume in-use

Status in OpenStack Compute (Nova):
  Invalid
Status in OpenStack Compute (nova) folsom series:
  Triaged

Bug description:
  This is similar to https://bugs.launchpad.net/ubuntu/+source/nova/+bug/954692 but still happens. Steps to reproduce on
  latest stable folsom:

  1. boot an instance
  2. create a volume
  3. attach the volume
  4. delete the instance before the attach is finished. For my test case it
     was about 1 second between attach and delete.

  The volume becomes stuck in "in-use".

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