yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #88458
[Bug 1829479] Fix included in openstack/nova 24.1.0
This issue was fixed in the openstack/nova 24.1.0 release.
** Changed in: nova/xena
Status: Fix Committed => Fix Released
--
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/1829479
Title:
The allocation table has residual records when instance is evacuated
and the source physical node is removed
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) xena series:
Fix Released
Bug description:
Description
===========
When the compute node service is down due to a failure, we choose to
evacuate instances located on it. After successful evacuation, the
relevant records in allocation table will not be cleared, it will only
be cleared when the compute service of the source node is restored.
Unfortunately, if the failure node is down because of some
unrecoverable failures, and compute service on it will never be
restored, there will be residual records in the allocation table.
Further more, if we try to delete the down compute service, record
associated with this service will not be deleted in reource_provider
table, because of the residual record in allocation table.
Perhaps after a successful evacuation, we need to add operations to
clear the allocation table, not just after the source node service is
restored.
Steps to reproduce
==================
1.down a compute service
2.evacuate the instances on it
3.delete compute service with command: nova service-delete uuid
Expected result
===============
compute service is deleted successful, and resource_provider has no
relevant record
Actual result
=============
compute service is deleted successful, but resource_provider still has
relevant record
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1829479/+subscriptions
References