You have been subscribed to a public bug:
Creating an octavia load-balancer with the ovn provider, adding a
health-monitor and then members, octavia creates a neutron hm port in each
subnet where a member was added.
Removing the members again, the hm ports do not get cleaned up. The hm removal
then cleans up one of the hm ports, the one that is in the subnet where the vip
happens to be. The others are still left and do not get cleaned up by octavia.
This of course will cause issues when subnets can later not be deleted due to
being still populated by the orphaned ports.
The cleanup logic simply does not match the hm port creation logic.
Mitigating factors:
* openstack loadbalancer delete --cascade does clean up all hm ports.
* Deleting the health mon before removing the members also avoids the issue.
** Affects: neutron
Importance: Undecided
Status: New
--
octavia/ovn: missed healthmon port cleanup
https://bugs.launchpad.net/bugs/2062965
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
--
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
