Volumes not cleaned up on rescheduled VM deploys
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Description:
When attempting to deploy an instance, if the instance fails to deploy on multiple hosts, the volumes are not cleaned up after the last deploy fails. The issue appears to only affect instances which fail an initial deploy and are rescheduled, and still ultimately fail for either NoValidHost or MaxRetriesExceeded. Instances which fail the initial deploy are cleaned up correctly.
Steps to Reproduce:
- Perform a virtual machine deploy that fails an initial deploy and attempts to reschedule.
- Raise an error during the reschedule.
Expected Result:
- Volumes should be cleaned up similarly to when exception are raised in nova.compute.
Actual Result:
- Volumes are not cleaned up and remain even after the virtual machine deploy fails.
Additional Notes:
In nova.conductor.
- https:/
In nova.compute.
- https:/
Environment:
- nova version: openstack-
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |