Hyper-V: planned vms are not cleaned up
Bug #1604078 reported by
Lucian Petrut
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Claudiu Belu | ||
compute-hyperv |
Fix Released
|
Medium
|
Unassigned | ||
os-win |
Fix Released
|
Medium
|
Unassigned |
Bug Description
We create a planned vm during live migration when having passthrough disks attached in order to properly configure the resources of the 'new' instance.
The issue is that if the migration fails, this planned vm is not cleaned up.
Although planned vms are destroyed at a second attempt to migrate the instance, this issue had an impact on the Hyper-V CI as planned vms persisted among CI runs and vms having the same name failed to spawn, as there were file handles kept open by the VMMS service, preventing the instance path from being cleaned up.
tags: | added: hyper-v |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in compute-hyperv: | |
importance: | Undecided → Medium |
Changed in os-win: | |
importance: | Undecided → Medium |
Changed in os-win: | |
status: | New → Fix Released |
To post a comment you must log in.
Need an update from the hyperv team on whether this is a real bug that can be addressed