Reviewed: https://review.openstack.org/554920 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=589c495c1ae62129e20ab5e2641e330541eee01f Submitter: Zuul Branch: master
commit 589c495c1ae62129e20ab5e2641e330541eee01f Author: Surya Seetharaman <[email protected]> Date: Wed Mar 21 14:16:24 2018 +0100 Cleanup RP and HM records while deleting a compute service. Currently when deleting a nova-compute service via the API, we will (soft) delete the service and compute_node records in the DB, but the placement resource provider and host mapping records will be orphaned. This patch deletes the resource provider and host_mapping records before deleting the service/compute node. Change-Id: I7b8622b178d5043ed1556d7bdceaf60f47e5ac80 Closes-Bug: #1756179 ** Changed in: nova Status: In Progress => 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/1756179 Title: deleting a nova-compute service leaves orphaned records in placement and host mapping Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: Confirmed Status in OpenStack Compute (nova) queens series: Confirmed Bug description: Currently when deleting a nova-compute service via the API, we will delete the service and compute_node records in the DB, but the placement resource provider and host mapping records will be orphaned. The orphaned resource provider records have been found to cause scheduler failures if you re-create the compute node with the same name (but a different UUID). It has been theorized that the stale host mapping records could end up pointing at the wrong cell. In discussions on IRC (http://eavesdrop.openstack.org/irclogs /%23openstack-nova/%23openstack- nova.2018-03-15.log.html#t2018-03-15T19:30:13) it was proposed that we should 1. delete the RP in placement 2. delete the host mapping 3. delete the service/node Optionally we could delete the compute node prior to deleting the service to make it explicit and because the ordering is slightly more logical, but this is not a requirement since it will be done implicitly as part of deleting the service. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1756179/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
