Bug 2159677

Summary: HM status not conditional on the status of the existing members
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)CC: ltomasbo
Target Milestone: gaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ovn-octavia-provider-1.0.3-1.20221227155353.0d529f7.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:13:10 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 2023-01-10 11:30:47 UTC 
Description of problem:
When a new HM is created for a LB (ovn-provider), it is checking the member status, if any of the member (ports related) is not found the HM is created with ERROR provisioning status. It doesn't make sense if we take into account that the HM is an independent entity and should not see its status conditioned by the status of the members it will monitor.

Steps to Reproduce:
1. Creation of a pool (pool1)
2. Creation of a member (member1) associated to the previous pool (pool1), which starts in ACTIVE
3. Creation of a member (member2) associated to the previous pool (pool1), which starts in ERROR status for example because we have invented the member address.
4. Creation of a HM associated to the pool (pool1)

Actual results:
as output the HM will be in ERROR.

Expected results:
If we do the same steps in a bulk request the output will be HM as ACTIVE and the members as expected (member1 ACTIVE, member2 ERROR)
Comment 6 Lukas Svaty 2023-06-16 08:13:29 UTC 
Bulk moving target milestone to GA after the release of Beta on 14th June '23.
Comment 13 errata-xmlrpc 2023-08-16 01:13:10 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