Description of problem: A problem was identified where removing a tenant can leave behind stray routers, ports, etc. For RHOSP customers this was solved till now by manually running a script. It was suggested that a simple 'neutron purge <tenant_id>' command or similar would simplify the process of cleaning up these stray resources by removing everything associated with the given tenant. The expectation is that this command would be admin-only, and neutron should not be responsible for deciding whether the action is 'safe'. It should work regardless of whether the given tenant is active or not.
The addition of the 'neutron purge' command allows cloud admins to conveniently delete multiple neutron resources associated with a given tenant. The command will delete all supported resources provided that they can be deleted (not in use, etc) and feedback the amount of each resource deleted to the user. A completion percentage is also given to keep the user informed of progress. Currently supports deletion of: *Networks *Subnets (implicitly) *Routers *Ports (including router interfaces) *Floating IPs *Security Groups
*** Bug 1270836 has been marked as a duplicate of this bug. ***
(In reply to Nir Yechiel from comment #2) > The addition of the 'neutron purge' command allows cloud admins to > conveniently delete multiple neutron resources associated with a given > tenant. > > The command will delete all supported resources provided that they can be > deleted (not in use, etc) and feedback the amount of each resource deleted > to the user. A completion percentage is also given to keep the user informed > of progress. > > Currently supports deletion of: > > *Networks > *Subnets (implicitly) > *Routers > *Ports (including router interfaces) > *Floating IPs > *Security Groups Hi Nir, Are the basic dependencies should prevent the command execution? For example- I cannot delete router (nor net/subnet) when we have ports attached to it. What is the expected behavior in this case? Tnx
(In reply to Alexander Stafeyev from comment #5) > (In reply to Nir Yechiel from comment #2) > > The addition of the 'neutron purge' command allows cloud admins to > > conveniently delete multiple neutron resources associated with a given > > tenant. > > > > The command will delete all supported resources provided that they can be > > deleted (not in use, etc) and feedback the amount of each resource deleted > > to the user. A completion percentage is also given to keep the user informed > > of progress. > > > > Currently supports deletion of: > > > > *Networks > > *Subnets (implicitly) > > *Routers > > *Ports (including router interfaces) > > *Floating IPs > > *Security Groups > > Hi Nir, > > Are the basic dependencies should prevent the command execution? > For example- I cannot delete router (nor net/subnet) when we have ports > attached to it. What is the expected behavior in this case? > > Tnx The command will delete all supported resources provided that **they can be deleted (not in use)**. Also, A resource being in use by another tenant (for example, a shared network) can prevent it from being deleted. Please see http://docs.openstack.org/mitaka/networking-guide/misc-neutron-purge.html
Ran on 2016-06-05 build - 2016-04-29.6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1597.html
*** Bug 1426006 has been marked as a duplicate of this bug. ***
*** Bug 1426450 has been marked as a duplicate of this bug. ***
*** Bug 1431098 has been marked as a duplicate of this bug. ***