Verified in 4.3.0-0.nightly-2019-12-23-120031 on 2019-12-06.2 OSP 13 puddle. The OCP installer finishes successfully: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2019-12-23-120031 True False 13h Cluster version is 4.3.0-0.nightly-2019-12-23-120031 insights-operator is newer then the kuryr-dns-admission-controller pods, as now insights-operator is restarted once the admission controller is ready, so it can be configured to use TCP instead of UDP for DNS resolution. $ oc get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE openshift-insights insights-operator-64559cfc5d-m9kk4 1/1 Running 3 16h openshift-kuryr kuryr-dns-admission-controller-5jggg 1/1 Running 0 16h openshift-kuryr kuryr-dns-admission-controller-grb46 1/1 Running 0 16h openshift-kuryr kuryr-dns-admission-controller-qrrd9 1/1 Running 0 16h $ oc -n openshift-insights describe pod insights-operator-64559cfc5d-m9kk4 | grep Started Started: Mon, 23 Dec 2019 13:44:46 -0500 Started: Mon, 23 Dec 2019 13:40:19 -0500 $ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-5jggg | grep Started Started: Mon, 23 Dec 2019 13:17:32 -0500 $ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-grb46 | grep Started Started: Mon, 23 Dec 2019 13:15:37 -0500 $ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-qrrd9 | grep Started Started: Mon, 23 Dec 2019 13:17:32 -0500 insights-operator is not showing error messages either.
Adding more info: $ oc -n openshift-insights get pod insights-operator-64559cfc5d-m9kk4 -o yaml | grep -A3 dnsConfig dnsConfig: options: - name: use-vc value: ""
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:0062