** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/pike
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova/pike
Importance: Undecided => Medium
--
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/1678056
Title:
RequestSpec records are never deleted when destroying an instance
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) ocata series:
New
Status in OpenStack Compute (nova) pike series:
In Progress
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]/reclaim_instance_interval for restoring
deleted instances), we could then delete the RequestSpec too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1678056/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
