yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

The Tokyo Summit solution here was that this should be done via an osc
plugin. There are really dramatic issues with auto delete from keystone
deletes. Many sites need an archive process. Nova itself soft deletes
many resources, and even has the ability to set an undo time on some of
them.

This shouldn't be an automatic process in the cloud, it should be
deliberate. Just like not deleting all the files on your system owned by
a user if you remove that user from /etc/passwd.

** Changed in: nova
       Status: Confirmed => Won't Fix

-- 
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/967832

Title:
  Resources owned by a project/tenant are not cleaned up after that
  project is deleted from keystone

Status in Glance:
  Confirmed
Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  If you have running instances in a tenant, then remove all the users,
  and finally delete the tenant, the instances are still running.
  Causing serious trouble, since nobody has access to delete them. Also
  affects the "instances" page in horizon. It will break if this
  scenario occurs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/967832/+subscriptions