Description of problem: After running a OpenShift cluster density test with Kuryr as SDN and having a fix[1] manually included that avoids load-balancer ending up with pending-* state, it was noted that a few load-balancers still remained with PENDING_CREATE state. (ostest) [stack@undercloud ~]$ openstack loadbalancer list |grep -i pending | cf1de73d-3ad0-4786-808a-f758728a7995 | 7357d50c-04d7-4be2-a2bb-607f4a5e6f6f-70/deployment-2pod-70-1 | 7c5afdccc3b24bfcb32ed6df3e87f55b | 172.30.235.21 | PENDING_CREATE | ovn | | e8960bd1-2846-43b1-9e30-1e0684946009 | 7357d50c-04d7-4be2-a2bb-607f4a5e6f6f-249/deployment-1pod-249-2 | 7c5afdccc3b24bfcb32ed6df3e87f55b | 172.30.211.105 | PENDING_CREATE | ovn | | 08a06df5-fcd6-4805-924c-4de67fc21e77 | 7357d50c-04d7-4be2-a2bb-607f4a5e6f6f-138/deployment-2pod-138-1 | 7c5afdccc3b24bfcb32ed6df3e87f55b | 172.30.243.207 | PENDING_CREATE | ovn [1] https://bugzilla.redhat.com/show_bug.cgi?id=2067069 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 16.2 2. 3. Actual results: Expected results: Additional info:
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 16.2.4), 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-2022:8794