Volumes are not detached when a build fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Andrew Laski |
Bug Description
When a build fails in the driver spawn method attached volumes are not detached. If the instance goes to ERROR and is later deleted everything gets cleaned up appropriately. If the instance is rescheduled then the next compute will fail with:
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:01.954 11008 TRACE nova.compute.
2014-06-18 20:09:02.002 11008 ERROR nova.compute.
which stops the build and properly stops a reschedule.
Cinder volumes need to be detached on a build failure.
Changed in nova: | |
importance: | Undecided → High |
status: | New → In Progress |
assignee: | nobody → Andrew Laski (alaski) |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/101335
Review: https:/