Errored instance can't be deleted if volume deleted first
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Ed Bak | ||
Havana |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
1. Create a bootable volume "nova volume-create --image-id <image_id> 10"
2. Boot a vm using the volume created in step 1 " nova boot --flavor 1 --image <image_id> --block-
If the instance fails to spawn in step 2, the instance ends up in an ERROR state. The volume goes back to available. The hard part is creating a situation in which step 2 fails. One way is to create enough quantum ports to exceed your port quota prior to attempting to spawn the instance.
3. Delete the volume.
4. Attempt to delete the instance. An exception gets thrown by driver.destroy because the volume is not found but the exception is not ignored and the instance can never be deleted. Exceptions from _cleanup_volumes get ignored for this same reason. I think another exception handler needs to be added to also ignore VolumeNotFound from driver.destroy.
I've reproduced this with current code from trunk.
Changed in nova: | |
assignee: | nobody → Ed Bak (ed-bak2) |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: havana-backport-potential |
Changed in nova: | |
milestone: | none → icehouse-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-1 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/45914
Review: https:/