"Orphan" request_specs and instance_mappings

Bug #1761198 reported by Belmiro Moreira on 2018-04-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Surya Seetharaman

Bug Description

request_specs and instance_mappings in nova_api DB are not removed when an instance is deleted.
In Queens they are removed when the instances are archived (https://review.openstack.org/#/c/515034/)

However, for the deployments that archived instances before running Queens they will have request_specs and instance_mappings that are not associated to any instance (they were already deleted).

We should have a nova-manage tool to clean these "orphan" records.

Changed in nova:
assignee: nobody → Surya Seetharaman (tssurya)
tags: added: cells nova-manag
tags: added: nova-manage
removed: nova-manag
Matt Riedemann (mriedem) wrote :

Per the cells meeting today, we should look at rolling this into the online_data_migrations routine so we can eventually remove it later, since once you get to Queens and archive does the cleanup for you, we won't need a separate command for this older record cleanup.

Matt Riedemann (mriedem) on 2018-04-04
Changed in nova:
importance: Undecided → Medium
status: New → Confirmed

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

Changed in nova:
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers