Description of problem: While running a cluster density test in a OpenShift cluster, Kuryr keeps retrying to create a load-balancer and failing because the address is already being used. The address is being used by a Port for the load-balancer, but no load-balancer actually exists. (ostest) [stack@undercloud ~]$ openstack port list |grep 172.30.125.1 | 6a9c24a2-7907-4b5c-b406-f74ba5a05820 | ovn-lb-vip-22efa8a7-460c-443f-8f53-ac53929e8637 | fa:16:3e:ea:e5:c4 | ip_address='172.30.125.1', subnet_id='beb4de56-a2b1-487b-9ab5-e10a0ad0d7ac' | DOWN | (ostest) [stack@undercloud ~]$ openstack loadbalancer list --vip-port-id ovn-lb-vip-22efa8a7-460c-443f-8f53-ac53929e8637 (ostest) [stack@undercloud ~]$ octavia.common.exceptions.ProviderDriverError: Provider 'ovn' reports error: IP address 172.30.125.1 already allocated in subnet beb4de56-a2b1-487b-9ab5-e10a0ad0d7ac Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified as in https://bugzilla.redhat.com/show_bug.cgi?id=2087204 python3-networking-ovn-7.4.2-2.20220409154863.el8ost.noarch RHOS-16.2-RHEL-8-20221104.n.0
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