Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1426450

Summary: clean up all resources when deleting a tenant
Product: Red Hat OpenStack Reporter: bigswitch <rhosp-bugs-internal>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED DUPLICATE QA Contact: Toni Freger <tfreger>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: amuller, chrisw, nyechiel, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-24 14:21:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bigswitch 2017-02-23 23:28:42 UTC 
Description of problem:

User can delete a project without cleaning up the resources attached to project (e.g network , subnets , security groups , floating IP allocated to project). This creates a problem for neutron sync , as neutron keep track of all the ports and does not have sync to keystone project to verify

e.g floating neutron IP ports  does not have any project association , How ever neutron floatingip-show <port> does have user project associated information. This creates inconsistency when user delete a project without cleaning up floating IP.

Version-Release number of selected component (if applicable):


How reproducible:
create a tenant 
create a network , subnet , allocate a floating IP
delete a tenant without cleaning up the network , subnet , floating IP.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Request to cleanup the all resources to the tenant before deleting a tenant 
Additional info:
Comment 1 Assaf Muller 2017-02-24 14:21:21 UTC 
Is this different from bug 1426006?

*** This bug has been marked as a duplicate of bug 1325678 ***