Tenant delete does not clean up the networks or VMs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
If a tenant has networks and VM instances created under it.
If tenant-delete is issued, it should either be rejected as there are objects under it or those objects should be automatically cleaned.
Neither of that takes place.
To reproduce this bug:
- Create a tenant (keystone tenant-create )
- create a network for this tenant (neutron net-create)
- Instantiate a VM for this tenant ( nova boot)
- Now delete the tenant (keystone tenant-delete)
This operation succeeds. However now you are left with a situation where you do not have a tenant, but, networks and VM belonging to it remain active.
This whole thing can be created from Horizon as well. The worst part about doing from Horizon is that you do dot see tenant and networks on horizon after the tenant is deleted.
| Mark McClain (markmcclain) wrote | #1 |
| Changed in neutron: | |
| status: | New → Won't Fix |
This is a known issue with all services in OpenStack. Due to the loose coupling between services there's no way to know a tenant has been removed. This is a cross project issue and would need a blueprint and design discussion in the keystone project.