yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53236
[Bug 1153827] Re: soft delete values in InstanceSystemMetadata on instance delete
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: Low => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
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/1153827
Title:
soft delete values in InstanceSystemMetadata on instance delete
Status in OpenStack Compute (nova):
Expired
Status in OpenStack Compute (nova) grizzly series:
Fix Released
Bug description:
soft delete values in InstanceSystemMetadata on instance delete.
Currently InstanceSystemMetadata is used in
notify_usage_exists_deleted_instance. Non-deleted
systemInstanceMetadta is currently used (with deleted instances).
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L755
In order to fix this the read_deleted flag needs to work for joined tables.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1153827/+subscriptions