unable to delete lbaasv2 health monitor if its listener deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Evgeny Fedoruk |
Bug Description
problem is in Kilo neutron-lbaas branch.
monitor is attached a pool.
When pool and listener were deleted, not error reported that there is a health-monitor associated to pool.
If all lbaas resoruces except health-monitor were deleted, health monitor can not be deleted.
See the following procedure to reproduce this issue:
$ neutron lbaas-loadbalan
$ neutron lbaas-listener-
$ neutron lbaas-pool-create --lb-algorithm=
$ neutron lbaas-member-create --subnet lb2-v-1574810802 --address 10.199.88.3 --protocol-port=80 v-lb2-pool
$ neutron lbaas-member-create --subnet lb2-v-1574810802 --address 10.199.88.4 --protocol-port=80 v-lb2-pool
$ neutron lbaas-healthmon
$ neutron lbaas-member-delete 4d2977fc-
$ neutron lbaas-member-delete 2f60a49b-
$ neutron lbaas-pool-delete v-lb2-pool
$ neutron lbaas-listener-
$ neutron lbaashealthmoni
neutron log seems point to lbaas resources were gone.
In this specific issue, we should just remove the health monitor from system.
2016-04-10 16:57:38.220 INFO neutron.wsgi [req-7e697943-
2016-04-10 16:57:38.252 ERROR neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.252 4158 TRACE neutron.
2016-04-10 16:57:38.253 INFO neutron.wsgi [req-aaeae392-
tags: | added: lbaas |
Changed in neutron: | |
assignee: | nobody → Evgeny Fedoruk (evgenyf) |
Looks like the lbaasv2 API needs to fail the pool delete request if the column neutron. lbaas_pools. healthmonitor_ id is populated for that pool. It obviously should return back to the user why and what healthmonitor needs to be deleted first.