Public bug reported: This is split off from bug 1829479 which is about deleting a compute service which had servers evacuated from it which will orphan resource providers in placement.
A similar scenario is true where the API will allow deleting a source compute service which has migration-based allocations for the source node resource provider and pending instance resizes involving the source node. A simple scenario is: 1. create a server on host1 2. resize or cold migrate it to a dest host2 3. delete the compute service for host1 At this point the resource provider for host1 is orphaned. 4. try to confirm/revert the resize of the server which will fail because the compute node for host1 is gone and this results in the server going to ERROR status Based on the discussion in this mailing list thread: http://lists.openstack.org/pipermail/openstack- discuss/2019-November/010843.html We should probably have the DELETE /os-services/{service_id} API block trying to delete a service that has pending migrations. ** Affects: nova Importance: Medium Status: Triaged ** Tags: api placement resize ** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1852610 Title: API allows source compute service/node deletion while instances are pending a resize confirm/revert Status in OpenStack Compute (nova): Triaged Bug description: This is split off from bug 1829479 which is about deleting a compute service which had servers evacuated from it which will orphan resource providers in placement. A similar scenario is true where the API will allow deleting a source compute service which has migration-based allocations for the source node resource provider and pending instance resizes involving the source node. A simple scenario is: 1. create a server on host1 2. resize or cold migrate it to a dest host2 3. delete the compute service for host1 At this point the resource provider for host1 is orphaned. 4. try to confirm/revert the resize of the server which will fail because the compute node for host1 is gone and this results in the server going to ERROR status Based on the discussion in this mailing list thread: http://lists.openstack.org/pipermail/openstack- discuss/2019-November/010843.html We should probably have the DELETE /os-services/{service_id} API block trying to delete a service that has pending migrations. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1852610/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
