RequestSpec records are never deleted when destroying an instance
Bug #1678056 reported by
Sylvain Bauza
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Surya Seetharaman | ||
Ocata |
New
|
Undecided
|
Unassigned | ||
Pike |
Fix Committed
|
Medium
|
Matt Riedemann |
Bug Description
When an instance is created, Nova adds a record in the API DB 'request_specs' table by providing the user request. That's used by the scheduler for knowing the boot request, also when the instance is moved afterwards.
That said, when destroying the instance, we don't delete the related RequestSpec record.
Of course, operators could run a script for deleting them by checking the instance UUIDs, but it would be better if when an instance is hard-deleted (ie. when operators don't use [DEFAULT]
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | Sylvain Bauza (sylvain-bauza) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | nobody → Sylvain Bauza (sylvain-bauza) |
status: | Triaged → In Progress |
tags: | added: pike-rc-potential scheduler |
Changed in nova: | |
assignee: | yuanyue (yyuanyuee) → Sylvain Bauza (sylvain-bauza) |
Changed in nova: | |
assignee: | Sylvain Bauza (sylvain-bauza) → Surya Seetharaman (tssurya) |
no longer affects: | nova/newton |
To post a comment you must log in.
There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments.