Description of problem: Openshift installation fails [stack@undercloud-0 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version False True 63m Unable to apply 4.4.0-0.nightly-2020-02-18-211831: an unknown error has occurred [stack@undercloud-0 ~]$ oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication Unknown Unknown True 50m cloud-credential 4.4.0-0.nightly-2020-02-18-211831 True False False 63m csi-snapshot-controller 4.4.0-0.nightly-2020-02-18-211831 False True False 31m dns 4.4.0-0.nightly-2020-02-18-211831 True False False 43m etcd 4.4.0-0.nightly-2020-02-18-211831 True False False 41m insights 4.4.0-0.nightly-2020-02-18-211831 True False False 50m kube-apiserver 4.4.0-0.nightly-2020-02-18-211831 True False False 46m kube-controller-manager 4.4.0-0.nightly-2020-02-18-211831 True False False 44m kube-scheduler 4.4.0-0.nightly-2020-02-18-211831 True False False 47m kube-storage-version-migrator 4.4.0-0.nightly-2020-02-18-211831 True False False 32m machine-api 4.4.0-0.nightly-2020-02-18-211831 True False False 47m machine-config 4.4.0-0.nightly-2020-02-18-211831 True False False 44m network 4.4.0-0.nightly-2020-02-18-211831 True False False 50m node-tuning 4.4.0-0.nightly-2020-02-18-211831 True False False 50m openshift-apiserver 4.4.0-0.nightly-2020-02-18-211831 False False True 50m openshift-controller-manager 4.4.0-0.nightly-2020-02-18-211831 True False False 48m operator-lifecycle-manager 4.4.0-0.nightly-2020-02-18-211831 True False False 47m operator-lifecycle-manager-catalog 4.4.0-0.nightly-2020-02-18-211831 True False False 47m operator-lifecycle-manager-packageserver 4.4.0-0.nightly-2020-02-18-211831 True False False 45m service-ca 4.4.0-0.nightly-2020-02-18-211831 True False False 50m service-catalog-apiserver 4.4.0-0.nightly-2020-02-18-211831 True False False 50m service-catalog-controller-manager 4.4.0-0.nightly-2020-02-18-211831 True False False 50m Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-02-18-211831 OSP16 RHOS_TRUNK-16.0-RHEL-8-20200213.n.1 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. Successful cluster installation, on OSP with octavia-ovn driver. $ openstack loadbalancer provider list +---------+-------------------------------------------------+ | name | description | +---------+-------------------------------------------------+ | amphora | The Octavia Amphora driver. | | octavia | Deprecated alias of the Octavia Amphora driver. | | ovn | Octavia OVN driver. | +---------+-------------------------------------------------+ The ovn-octavia support is detected: 2020/04/02 09:44:28 Checking OVN Octavia driver support 2020/04/02 09:44:28 Detected Octavia API v2.13.0 2020/04/02 09:44:28 Checking Double Listeners Octavia support 2020/04/02 09:44:28 Detected Octavia API v2.13.0 and the admission controllers are deployed, as the double listeners are not supported: $ oc -n openshift-kuryr get pods NAME READY STATUS RESTARTS AGE kuryr-cni-66s8s 1/1 Running 2 23h kuryr-cni-8mxjn 1/1 Running 4 23h kuryr-cni-djftq 1/1 Running 2 23h kuryr-cni-dljgh 1/1 Running 2 23h kuryr-cni-qmx6x 1/1 Running 2 23h kuryr-cni-rs2gw 1/1 Running 4 23h kuryr-controller-694dc6fb45-xqjw8 1/1 Running 8 21h kuryr-dns-admission-controller-7wnkt 1/1 Running 0 23h kuryr-dns-admission-controller-knzq8 1/1 Running 0 23h kuryr-dns-admission-controller-vnrg6 1/1 Running 0 23h
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