yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #24614
[Bug 1390102] Re: Block device mapping not deleted
Thanks, it seems to be fixed now. Closing
** Changed in: nova
Status: Incomplete => Invalid
--
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/1390102
Title:
Block device mapping not deleted
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Deleting an instance does not mark the block device mapping as deleted.
For example, boot an instance ( type doesn't matter, I found this on an ephemeral instance) then
delete the instance.
In the database, you see that "deleted=1" for the instance, but for the corresponding entry in block_device_mapping is not deleted
This becomes a problem during archive_deleted_rows, or in the proposed
purge_deleted_rows because of a foreign key constraint
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1390102/+subscriptions
References