Remove leftover OVN LB HM port upon deletion of a member
When a load balancer pool has a Health Monitor associated with it,
an OVN LB Health Monitor port is created for each backend member
subnet added.
When removing backend members, the OVN LB Health Monitor port is
cleaned up only if no more members are associated with the Health
Monitor pool. However, this assumption is incorrect. This patch
corrects this behavior by checking instead if there are more members
from the same subnet associated with the pool. It ensures that the
OVN LB Health Monitor port is deleted only when the last member from
the subnet is deleted. If the port is being used by another different
LB Health Monitor, `_clean_up_hm_port` will handle it.
Reviewed: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/916637 /opendev. org/openstack/ ovn-octavia- provider/ commit/ f034bab144b68cf 96c538339e389c4 cc7c6d7d63
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit f034bab144b68cf 96c538339e389c4 cc7c6d7d63
Author: Fernando Royo <email address hidden>
Date: Mon Apr 22 15:47:46 2024 +0200
Remove leftover OVN LB HM port upon deletion of a member
When a load balancer pool has a Health Monitor associated with it,
an OVN LB Health Monitor port is created for each backend member
subnet added.
When removing backend members, the OVN LB Health Monitor port is
cleaned up only if no more members are associated with the Health
Monitor pool. However, this assumption is incorrect. This patch
corrects this behavior by checking instead if there are more members
from the same subnet associated with the pool. It ensures that the
OVN LB Health Monitor port is deleted only when the last member from
the subnet is deleted. If the port is being used by another different
LB Health Monitor, `_clean_up_hm_port` will handle it.
Closes-Bug: #2062965 b208f4313bb86e3 519df0a30fa
Change-Id: I4c35cc5c6af14b