Bug 2149216

Summary: HM not working for FIPs
Product: Red Hat OpenStack Reporter: Luis Tomas Bolivar <ltomasbo>
Component: python-ovn-octavia-providerAssignee: Luis Tomas Bolivar <ltomasbo>
Status: CLOSED ERRATA QA Contact: Omer Schwartz <oschwart>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: jamsmith, joflynn, juriarte, mdemaced, mgeary, oschwart, rheslop
Target Milestone: betaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ovn-octavia-provider-1.0.3-1.20230302173806.8aff429.el9ost Doc Type: Bug Fix
Doc Text:
Before this update, Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated with the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. + With this update, if you use Floating IPs (FIP) associated with the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:12:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luis Tomas Bolivar 2022-11-29 08:41:46 UTC 
When an OVN Load Balancer has HealthMonitors associated to its pool/members, if a member is detected as error, there is not traffic being sent to it.

However, if the OVN LoadBalancer has a FIP associated to the VIP, when using the FIP to access the Load Balancer, the traffic is loadbalanced also using the members that are in error status.
Comment 21 errata-xmlrpc 2023-08-16 01:12:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577