Cannot Delete loadbalancers due to undeleteable pools
Bug #1603458 reported by
Tyler Britten
This bug affects 11 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Neutron LBaaS Dashboard |
Confirmed
|
Undecided
|
Unassigned | ||
OpenStack Dashboard (Horizon) |
Invalid
|
Undecided
|
Unassigned | ||
neutron |
Invalid
|
Undecided
|
Unassigned |
Bug Description
To delete an LBaaSv2 loadbalancer, you must remove all the members from the pool, then delete the pool, then delete the listener, then you can delete the loadbalancer. Currently in Horizon you can do all of those except delete the pool. Since you can't delete the pool, you can't delete the listener, and therefore can't delete the loadbalancer.
Either deleting the listener should trigger the pool delete too (since they're 1:1) or the Horizon Wizard for Listener should have a delete pool capability.
Changed in neutron-lbaas-dashboard: | |
status: | Invalid → Confirmed |
To post a comment you must log in.
I believe this is an issue with the neutron- lbaas-dashboard , the neutron lbaas API does allow this. I was gonna mark this as Invalid, but the neutron- lbaas-dashboard does not live in horizon, it lives as a separate repo. I guess it does fall under neutron's purview for now.