42f62f1ed2
This change makes "DELETE /os-services/{service_id}" fail
with a 409 response when attempting to delete a nova-compute
service which is still hosting instances.
Deleting a compute service also results in deleting the
related compute_nodes table entry for that service host.
The compute node resource provider in placement is tied
to the compute node via the UUID, and if we allow deleting
the compute service and node then the resource provider for
that node is effectively orphaned in Placement, along with
the instances which have allocations against that resource
provider.
Furthermore, restarting the compute service will create a
new service and compute_nodes record, and the compute node
would have a new UUID and resource provider. This will
affect scheduling for that host since Placement will be
reporting it as having available capacity which in reality
is not accurate.
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. Since this API did not previously expect to return
a 409 response, the "expected_errors" decorator is updated
and again, should not require a microversion per the
guidelines:
https://docs.openstack.org/nova/latest/contributor/microversions.html#when-a-microversion-is-not-needed
Change-Id: I0bd63b655ad3d3d39af8d15c781ce0a45efc8e3a
Closes-Bug: #1763183
10 lines
468 B
YAML
10 lines
468 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 still hosting instances. This is because doing so would
|
|
orphan the compute node resource provider in the placement service on
|
|
which those instances have resource allocations, which affects scheduling.
|
|
See https://bugs.launchpad.net/nova/+bug/1763183 for more details.
|