When deleting a resource provider in the placement api the rp's associated aggregates are not cleaned up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Ed Leafe |
Bug Description
When deleting a resource provider the spec says that the resource provider's inventory and associated aggregates should be deleted:
In version 1.1 of the placement API, inventory is being deleted, but aggregate associations are left untouched. This means that in the following case the resulting aggregates will be wrong:
* create an rp with a known uuid (this is allowed and expected)
* associate some aggregates (a, b, c)
* delete the rp
* recreate the rp with same uuid
* query the associated aggregates get 'a, b, c' but expect []
Note that the set_aggregates functionality (and the associated PUT API) is a full replace so any time the associated aggregates are updated, the input in that request becomes the whole set of associated aggregates. This bug is only present in the case where aggregates were present on the previous incarnation of a resource provider but should not be on the current incarnation.
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
See the _get_aggregates and _delete methods on the ResourceProvider object in nova.objects. resource_ provider for more details.