Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2131672

Summary: ServiceMonitorUpdate events affecting to unrelated load balancers
Product: Red Hat OpenStack Reporter: Fernando Royo <froyo>
Component: python-ovn-octavia-providerAssignee: Fernando Royo <froyo>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)Keywords: Triaged
Target Milestone: z1   
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ovn-octavia-provider-1.0.1-0.20221122190308.bbf881f.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-25 12:29:56 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 Fernando Royo 2022-10-03 08:29:35 UTC 
When an ServiceMonitorUpdateEvent happens, it is affecting to all loadbalancers that have the member ip in its list of members, regardless of the affected port.

Reproducible via:

- Create two VMs with services running on port 80 and 22
- Create two lb over the same VMs but listener on different port (80 and 22)
- Create two hm, one for the lb over port 80 and another one for lb on port 22
- Stop the service responding on port 80 in one VM
- When the ServiceMonitorUpdateEvent is triggered over the VM:80, the lb for the port 80 updates the member status to ERROR, but the other lb over port 22 also does, although port 22 is still responsive.
Comment 12 errata-xmlrpc 2023-01-25 12:29:56 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 (Red Hat OpenStack Platform 17.0.1 bug fix and enhancement advisory), 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/RHBA-2023:0271