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.5.0-0.nightly-2020-04-02-004321 on top of OSP 16 RHOS_TRUNK-16.0-RHEL-8-20200324.n.0 compose. 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-04-02T08:16:30Z" name: kuryr-config namespace: openshift-kuryr ownerReferences: - apiVersion: operator.openshift.io/v1 blockOwnerDeletion: true controller: true kind: Network name: cluster uid: 42ce3d14-9dce-418b-ad9f-bbfcbeb34cfb resourceVersion: "3085" selfLink: /api/v1/namespaces/openshift-kuryr/configmaps/kuryr-config uid: a019788e-6323-4cea-8593-e25fadc1029d If the config-map is edited (with a different value): networkoperator.openshift.io/kuryr-octavia-provider: "" it will be updated correctly with reconciliation: 2020/04/03 08:53:37 Checking OVN Octavia driver support 2020/04/03 08:53:37 Detected Octavia API v2.13.0 2020/04/03 08:53:37 Checking Double Listeners Octavia support 2020/04/03 08:53:37 Detected Octavia API v2.13.0 2020/04/03 08:53:37 OVN Provider is enabled and Kuryr will use it 2020/04/03 08:53:37 Kuryr bootstrap finished 2020/04/03 08:53:37 Starting render phase 2020/04/03 08:53:37 Render phase done, rendered 37 objects 2020/04/03 08:53:37 reconciling (/v1, Kind=ConfigMap) openshift-network-operator/applied-cluster 2020/04/03 08:53:37 update was successful $ oc get cm kuryr-config -n openshift-kuryr -o yaml ... metadata: annotations: networkoperator.openshift.io/kuryr-octavia-provider: ovn creationTimestamp: "2020-04-02T08:16:30Z" name: kuryr-config namespace: openshift-kuryr ownerReferences: - apiVersion: operator.openshift.io/v1 blockOwnerDeletion: true controller: true kind: Network name: cluster uid: 42ce3d14-9dce-418b-ad9f-bbfcbeb34cfb resourceVersion: "514532" selfLink: /api/v1/namespaces/openshift-kuryr/configmaps/kuryr-config uid: a019788e-6323-4cea-8593-e25fadc1029d
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:2409