yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81032
[Bug 1852610] Re: API allows source compute service/node deletion while instances are pending a resize confirm/revert
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/stein
Importance: Undecided => Medium
** Changed in: nova/train
Importance: Undecided => Medium
** Changed in: nova/rocky
Importance: Undecided => Medium
** Changed in: nova/queens
Importance: Undecided => Low
--
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):
Fix Released
Status in OpenStack Compute (nova) queens series:
Confirmed
Status in OpenStack Compute (nova) rocky series:
In Progress
Status in OpenStack Compute (nova) stein series:
Fix Committed
Status in OpenStack Compute (nova) train series:
Fix Committed
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
References