yahoo-eng-team team mailing list archive

[Abel Lopez <alopgeek@xxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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):
  New

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