Purge the compute_node records, resource provider records and host_mappings when doing force delete of the host

Bug #1749734 reported by Surya Seetharaman on 2018-02-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Surya Seetharaman

Bug Description

The nova-manage cell_v2 delete_cell --force option currently only removes the host_mappings of empty hosts before deleting the cell. This has to be extended to deleting the nova.compute_nodes record and nova_api.resource_providers along with the host_mappings for those hosts which have no living instances.

The nova-manage cell_v2 delete_host needs to have a new option --force by which when a host is deleted forcefully, if it has no living instances then again its nova.compute_node record and nova_api.resource_provider along with its host_mapping should be removed.

description: updated
Matt Riedemann (mriedem) on 2018-02-15
tags: added: cells
Changed in nova:
status: New → Incomplete
status: Incomplete → Confirmed
importance: Undecided → Medium

Fix proposed to branch: master
Review: https://review.openstack.org/546660

Changed in nova:
status: Confirmed → In Progress
Matt Riedemann (mriedem) wrote :

This is arguably a duplicate of bug 1756179 which is already resolved now - DELETE /os-services/{id} will now delete resource provider and host mapping for a compute service record when deleting the service via the REST API.

Surya Seetharaman (tssurya) wrote :

Since implementing this on delete_host command would make this a copy of nova service-list, we now focus only on delete_cell; tbh I am not sure what's the goal of having delete_host.. maybe to just delete the host_mapping and re-create the host mapping in the same cell? -> wondering what's the use case for that.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers