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)
Bulk moving target milestone to GA after the release of Beta on 14th June '23.
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