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

Bug #1096197 reported by David Kranz
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
High
Unassigned

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

Changed in nova:
status: New → Triaged
importance: Undecided → High
milestone: none → grizzly-rc1
Revision history for this message
Vish Ishaya (vishvananda) wrote :

needs to be verified against folsom

Changed in nova:
milestone: grizzly-rc1 → none
status: Triaged → Invalid
Revision history for this message
Vish Ishaya (vishvananda) wrote :

I was unable to reproduce on master

Revision history for this message
Yun Mao (yunmao) wrote :

What does "stuck in in-use" mean? The volume can no longer be detached? Thanks.

Revision history for this message
David Kranz (david-kranz) wrote :

Yes, the instance is gone and then the volume cannot be attached to another instance. It cannot be deleted either, presumably because its state is IN-USE. I had to manually change its state in the database in order to delete it.

Revision history for this message
Yun Mao (yunmao) wrote :

I also can't reproduce it, but it seems like a sound fix would be at the detach phase, if the VM is already deleted, the detach should succeed. Make sense?

Sean Dague (sdague)
no longer affects: nova/folsom
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers