Ports are not being deleted with clusters
Bug #1448140 reported by
Davide Agnello
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cue |
Fix Committed
|
High
|
Unassigned |
Bug Description
Executing a cluster creation test with a Rally benchmark of 100x in Devstack reviled ports are not being deleted when respective clusters are being deleted. This test reached the port creation limit which then led to Cluster creation failures due to no being able to create new ports.
Possible solution:
The Cluster Delete work flow should also explicitly delete a Cluster's associated ports.
Changed in cue: | |
importance: | Undecided → High |
To post a comment you must log in.
Verified issue.
Scenario 1:
1. Created two ports
2. Created a VM and attached both ports from step 1
3. Verified both networks are connected to new VM
4. Issued delete of VM
5. Verified VM was deleted
6. Verified two ports created in step 1 are still around (Cue assumption was ports would be deleted)
Scenario 2:
1. Created one port
2. Created a VM and attached port from step 1
3. Verified network is connected to new VM
4. Issued delete of VM
5. Verified VM was deleted
6. Verified port created in step 1 is still around (should be deleted as per Cue's assumption)