[RFE]: neutron purge- shared network without ports in non owner tenant

[Alex Stafeyev]

When we execute "neutron purge tenantID" on a tenant who has shared its network, and that network is in use by another tenant, the network will not be deleted.

When we execute "neutron purge tenantID" on a tenant who has shared its network, and that network is NOT in use by another tenant (seen by it but no ports attached to VMs nor routers), the network will be deleted without any warning message to the user.

We believe that there should be a message verifying the action:

Something like: "This network <ID> may be used by tenants <tenants ID>, are you sure you want to delete this network?

BR
Alex

[John Davidge (john-davidge)]

The list of tenants who MIGHT be using the network would likely just be every other tenant that exists. Would a message simply saying "Network <ID> is shared. Are you sure you wish to delete it?" be acceptable to you?

[Alex Stafeyev (astafeye)]

Yes, seems fine by me.

BR

[Akihiro Motoki (amotoki)]

"ospurge" project provides a tool to purge a project for various services. It looks better to improve it based on the bug reported here.

OpenStack client (OSC) is also implementing 'purge' command in https://review.openstack.org/#/c/367673/ .

[Akihiro Motoki (amotoki)]

I added OSC and ospurge to the affected projects. This bug report was filed against 'neutron purge' command, but OSC and ospurge has / will have similar feature and it is worth considered.

Regarding neutron purge command, neutron CLI is deprecated and the neutron team has no clear plan on fixing this bug. If a nice approach is proposed, we can accept it.