"Orphan" request_specs and instance_mappings
Bug #1761198 reported by
Belmiro Moreira
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Medium
|
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:/
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 |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #1 |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #2 |
| Changed in nova: | |
| status: | Confirmed → In Progress |
To post a comment you must log in.
Per the cells meeting today, we should look at rolling this into the online_