Marking this invalid as you can delete a pool via horizon. Did you
remember to delete the health monitor first?
I agree that in the future we could enable the cascade delete feature in
horizon with a warning, but that would be an RFE and not the bug as
reported. Closing this as invalid as you can in fact delete pools via
the neutron-lbaas-dashboard.
** Changed in: horizon
Status: New => Invalid
** Changed in: neutron-lbaas-dashboard
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1603458
Title:
Cannot Delete loadbalancers due to undeleteable pools
Status in OpenStack Dashboard (Horizon):
Invalid
Status in neutron:
Invalid
Status in Neutron LBaaS Dashboard:
Invalid
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1603458/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
