ovn-octavia-provider/releasenotes/notes/lbhc-fix-fip-05820d5a9d94a919.yaml
Fernando Royo ebfbd848b1 Fix port for Load Balancer Health Check for FIP
Currently when a FIP is attached to LB VIP after a HM is already
created, the LB_HC created for the new FIP is not including the
port in the vip field. At this way, when a member is in ERROR
operating status, request over the FIP are still distribute
to the ERROR'ed members.

This patch add the port when the FIP is associated to the LB VIP.

Related-Bug: #1997418
Change-Id: Iefe5d67b5a8fc47972b14c4247c381d625efcc09
2023-07-13 14:08:16 +00:00

16 lines
806 B
YAML

---
issues:
- |
Load Balancer Health Check for Floating IPs are not populated with the
protocol port. At this way, when a backend is detected on ERROR state
requests to the Floating IP are still distribute to the ERROR'ed members.
In order to fix the existing Load Balancer Health Checks it is required to
recreate the entire Octavia Health Monitor, which will recreate the
associated OVN Load Balancer Health Check(s).
fixes:
- |
[`bug 1997418 <https://bugs.launchpad.net/neutron/+bug/1997418>`_]
Added the protocol port to the Load Balancer Health Check associated with
the Floating IP, additional fields have been introduced to the external_ids
to provide more accuracy information about the entities affected by any
change over the Floating IP or LB VIP.