+++ This bug was initially created as a clone of Bug #1811104 +++ +++ 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.3.0-0.nightly-2020-03-23-130439 on top of OSP 16 RHOS_TRUNK-16.0-RHEL-8-20200226.n.1 and on top of OSP 13 2020-03-10.1 puddles. OSP 16 ====== CNO logs: 2020/03/24 10:51:14 Detected Octavia API v2.13.0 Kuryr pods: $ oc -n openshift-kuryr get pods NAME READY STATUS RESTARTS AGE kuryr-cni-5h6mk 1/1 Running 1 69m kuryr-cni-9bktx 1/1 Running 0 69m kuryr-cni-dgdzm 1/1 Running 0 46m kuryr-cni-dxkpj 1/1 Running 0 50m kuryr-cni-vmpd7 1/1 Running 0 49m kuryr-cni-xpvpt 1/1 Running 0 69m kuryr-controller-64c9df7b7b-8q9jj 1/1 Running 1 69m As Octavia API v2.13.0 has been detected (> v2.11) there is no need to deploy admission controller pods, as double loadbalancer listeners are supported (for port 53): $ openstack loadbalancer listener list --loadbalancer e7a5dade-8b62-42c2-838f-db33a6e6d01a +--------------------------------------+--------------------------------------+------------------------------------+----------+---------------+----------------+ | id | default_pool_id | name | protocol | protocol_port | admin_state_up | +--------------------------------------+--------------------------------------+------------------------------------+----------+---------------+----------------+ | 3e21cd04-9106-4f51-aed0-40f5a93d5030 | 7568078c-24b4-4c5a-a048-40bb59b6d623 | openshift-dns/dns-default:TCP:53 | TCP | 53 | True | | 15c1fa2a-190b-47c6-890c-ec2c1df2ef26 | 393210c6-e48a-48f2-9fbb-1fa3b129078c | openshift-dns/dns-default:TCP:9153 | TCP | 9153 | True | | d62ef200-6439-4e70-80c0-5ac15b211229 | ce96cf26-6d97-4282-a427-af778551d2bf | openshift-dns/dns-default:UDP:53 | UDP | 53 | True | +--------------------------------------+--------------------------------------+------------------------------------+----------+---------------+----------------+ OSP 13 ====== CNO logs: 2020/03/24 10:46:54 Detected Octavia API v2.0.0 Kuryr pods: $ oc -n openshift-kuryr get pods NAME READY STATUS RESTARTS AGE kuryr-cni-6ckks 1/1 Running 1 95m kuryr-cni-6spll 1/1 Running 0 95m kuryr-cni-dw6v2 1/1 Running 2 81m kuryr-cni-nxrgv 1/1 Running 0 95m kuryr-cni-p7jm2 1/1 Running 1 83m kuryr-cni-wzjcd 1/1 Running 1 79m kuryr-controller-64c9df7b7b-vtmjb 1/1 Running 1 95m kuryr-dns-admission-controller-9s28z 1/1 Running 0 95m kuryr-dns-admission-controller-9sgfh 1/1 Running 0 95m kuryr-dns-admission-controller-gdpds 1/1 Running 0 95m As Octavia API v2.0.0 has been detected (< v2.11) admission controller pods are needed, as double loadbalancer listeners are not supported: $ openstack loadbalancer listener list --loadbalancer 9a2f8a22-f126-4d4d-a48d-6470fd0f2b06 +--------------------------------------+--------------------------------------+------------------------------------+----------+---------------+----------------+ | id | default_pool_id | name | protocol | protocol_port | admin_state_up | +--------------------------------------+--------------------------------------+------------------------------------+----------+---------------+----------------+ | 52168a55-32b1-4d4d-8e7d-d61653bc1a1f | a2f38eb1-8064-4f70-a61e-9d285ac30c71 | openshift-dns/dns-default:TCP:53 | TCP | 53 | True | | 6ebd8c79-31e3-4eb7-830e-0090a949de42 | 0ee6b92b-c735-469c-a438-df37710ab096 | openshift-dns/dns-default:TCP:9153 | TCP | 9153 | True | +--------------------------------------+--------------------------------------+------------------------------------+----------+---------------+----------------+
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:0930