XEN: Volume VDIs not cleaned up if boot fails before VBD creation
Bug #1329941 reported by
Andrew Laski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Andrew Laski | ||
Bug Description
During the spawn process the rollback portion of the create_vm_record step is supposed to detach volumes, destroy the VBDs, and then purge the SR. But this process relies on looking up VBDs attached to the instance. If the spawn process fails while creating/resizing a VDI then there's no VBD to lookup and the SR and VDI will be left on the hypervisor as orphans.
| Changed in nova: | |
| assignee: | nobody → Andrew Laski (alaski) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → juno-2 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit be58dd8432a8d12
Author: Andrew Laski <email address hidden>
Date: Fri Jun 13 17:15:00 2014 -0400
Xen: Cleanup orphan volume connections on boot failure
If the boot process fails after the VDI creation but before a VBD is
created then the current cleanup methods will not work as they all rely
on lookups via VBD.
Change-Id: Id0d93ee60f75bf
Closes-bug: #1329941