+++ This bug was initially created as a clone of Bug #1811022 +++ Description of problem: We are using a Network client to retrieve the Octavia API version when a Load Balancer client should be used. This results in a wrong API version detection when checking if OVN Octavia driver is supported and if double listeners is supported. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified in 4.4.0-0.nightly-2020-03-13-073111 on top of OSP 16 RHOS_TRUNK-16.0-RHEL-8-20200226.n.1 ovn octavia is enabled: $ openstack loadbalancer provider list +---------+-------------------------------------------------+ | name | description | +---------+-------------------------------------------------+ | amphora | The Octavia Amphora driver. | | octavia | Deprecated alias of the Octavia Amphora driver. | | ovn | Octavia OVN driver. | +---------+-------------------------------------------------+ OVN Octavia driver detection worked during installation: $ oc get cm kuryr-config -n openshift-kuryr -o yaml ... metadata: annotations: networkoperator.openshift.io/kuryr-octavia-provider: ovn << ----------- creationTimestamp: "2020-03-13T15:48:29Z" name: kuryr-config namespace: openshift-kuryr ownerReferences: - apiVersion: operator.openshift.io/v1 blockOwnerDeletion: true controller: true kind: Network name: cluster uid: 491fb233-c263-4cc8-a3fe-2c3dc2f15cac resourceVersion: "2860" selfLink: /api/v1/namespaces/openshift-kuryr/configmaps/kuryr-config uid: 01483243-98ce-42db-ad23-ea5fd775ae32 If the config-map is edited (with a different value): networkoperator.openshift.io/kuryr-octavia-provider: "" it will be updated correctly with reconciliation: $ oc get cm kuryr-config -n openshift-kuryr -o yaml ... metadata: annotations: networkoperator.openshift.io/kuryr-octavia-provider: ovn creationTimestamp: "2020-03-13T15:48:29Z" name: kuryr-config namespace: openshift-kuryr ownerReferences: - apiVersion: operator.openshift.io/v1 blockOwnerDeletion: true controller: true kind: Network name: cluster uid: 491fb233-c263-4cc8-a3fe-2c3dc2f15cac resourceVersion: "2860" selfLink: /api/v1/namespaces/openshift-kuryr/configmaps/kuryr-config uid: 01483243-98ce-42db-ad23-ea5fd775ae32
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, 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-2020:0581