yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #62821
[Bug 1678056] [NEW] RequestSpec records are never deleted when destroying an instance
Public bug reported:
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.
** Affects: nova
Importance: High
Assignee: Sylvain Bauza (sylvain-bauza)
Status: In Progress
--
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):
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
Follow ups