[Yahoo-eng-team] [Bug 1526964] Re: Can delete lbaas-pool with lbaas-hm attached
*** This bug is a duplicate of bug 1571097 *** https://bugs.launchpad.net/bugs/1571097 ** This bug is no longer a duplicate of bug 1450375 cannot delete v2 healthmonitor if the hm-associated-pool was deleted first ** This bug has been marked a duplicate of bug 1571097 unable to delete lbaasv2 health monitor if its listener deleted -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526964 Title: Can delete lbaas-pool with lbaas-hm attached Status in neutron: Confirmed Bug description: Using the lbaas v2 resources, I created a loadbalancer, listener, pool, and healthmonitor, all attached to each other as expected. Next I deleted the pool, which I wouldn't expect to work since there is a healthmonitor attached to it, yet it worked successfully. Now I am unable to do anything with the healthmonitor that is remaining. I tried deleting the healthmonitor, only to get this error: $ neutron lbaas-healthmonitor-delete d7257837-7b76-4f70-836d-97dbfa7d5a4a Request Failed: internal server error while processing your request. $ Looking through the logs I grabbed this stack trace http://paste.openstack.org/show/482123/ The healthmonitor is unable to locate the pool it was attached to, since it has been deleted. Looking through the v1 code, it seems there was a check to make sure the pool was able to be deleted: https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_db.py#L619 This check does not exist in the v2 code however: https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_dbv2.py#L468 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526964/+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
[Yahoo-eng-team] [Bug 1526964] Re: Can delete lbaas-pool with lbaas-hm attached
*** This bug is a duplicate of bug 1450375 *** https://bugs.launchpad.net/bugs/1450375 ** This bug is no longer a duplicate of bug 1571097 unable to delete lbaasv2 health monitor if its listener deleted ** This bug has been marked a duplicate of bug 1450375 cannot delete v2 healthmonitor if the hm-associated-pool was deleted first -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526964 Title: Can delete lbaas-pool with lbaas-hm attached Status in neutron: Confirmed Bug description: Using the lbaas v2 resources, I created a loadbalancer, listener, pool, and healthmonitor, all attached to each other as expected. Next I deleted the pool, which I wouldn't expect to work since there is a healthmonitor attached to it, yet it worked successfully. Now I am unable to do anything with the healthmonitor that is remaining. I tried deleting the healthmonitor, only to get this error: $ neutron lbaas-healthmonitor-delete d7257837-7b76-4f70-836d-97dbfa7d5a4a Request Failed: internal server error while processing your request. $ Looking through the logs I grabbed this stack trace http://paste.openstack.org/show/482123/ The healthmonitor is unable to locate the pool it was attached to, since it has been deleted. Looking through the v1 code, it seems there was a check to make sure the pool was able to be deleted: https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_db.py#L619 This check does not exist in the v2 code however: https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_dbv2.py#L468 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526964/+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
