92fed02610
This builds on I0bd63b655ad3d3d39af8d15c781ce0a45efc8e3a
which made DELETE /os-services/{service_id} fail with a 409
response if the host has instances on it. This change checks
for in-progress migrations involving the nodes on the host,
either as the source or destination nodes, and returns a 409
error response if any are found.
Failling to do this can lead to orphaned resource providers
in placement and also failing to properly confirm or revert
a pending resize or cold migration.
A release note is included for the (justified) behavior
change in the API. A new microversion should not be required
for this since admins should not have to opt out of broken
behavior.
Change-Id: I70e06c607045a1c0842f13069e51fef438012a9c
Closes-Bug: #1852610
11 lines
541 B
YAML
11 lines
541 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The ``DELETE /os-services/{service_id}`` compute API will now return a
|
|
``409 HTTPConflict`` response when trying to delete a ``nova-compute``
|
|
service which is involved in in-progress migrations. This is because doing
|
|
so would not only orphan the compute node resource provider in the
|
|
placement service on which those instances have resource allocations but
|
|
can also break the ability to confirm/revert a pending resize properly.
|
|
See https://bugs.launchpad.net/nova/+bug/1852610 for more details.
|