e5a34fffdf
When a compute node goes down and all instances on the compute node are evacuated, allocation records about these instance are still left in the source compute node until nova-compute service is again started on the node. However if a compute node is completely broken, it is not possible to start the service again. In this situation deleting nova-compute service for the compute node doesn't delete its resource provider record, and even if a user tries to delete the resource provider, the delete request is rejected because allocations are still left on that node. This change ensures that remaining allocations left by successful evacuations are cleared when deleting a nova-compute service, to avoid any resource provider record left even if a compute node can't be recovered. Migration records are still left in 'done' status to trigger clean-up tasks in case the compute node is recovered later. Closes-Bug: #1829479 Change-Id: I3ce6f6275bfe09d43718c3a491b3991a804027bd
9 lines
381 B
YAML
9 lines
381 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #1829479 <https://bugs.launchpad.net/nova/+bug/1829479>`_: Now
|
|
deleting a nova-compute service removes allocations of successfully
|
|
evacuated instances. This allows the associated resource provider to be
|
|
deleted automatically even if the nova-compute service cannot recover after
|
|
all instances on the node have been successfully evacuated.
|