Failed unshelve does not remove allocations from destination node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann | ||
Pike |
Fix Committed
|
High
|
Matt Riedemann |
Bug Description
During an unshelve from an offloaded instance, conductor will call the scheduler to pick a host. The scheduler will make allocations against the chosen node as part of that select_
If the spawn on the hypervisor fails while we've made the instance claim:
https:/
Or even if the claim test fails, the allocations on the destination node aren't removed in Placement.
The RT aborts the claim here:
https:/
That calls _update_
https:/
And we don't cleanup the allocations for the instance.
The other case is if the claim fails, the instance_claim method will raise ComputeResource
https:/
https:/
But we don't remove allocations or do any other cleanup there.
Related fix proposed to branch: master /review. openstack. org/506414
Review: https:/