Description of problem: install ocp with http proxy failed with below error thrown from flexy job console output: + '/home/installer4/workspace/Launch Environment Flexy/workdir/openshift-install' wait-for install-complete --dir '/home/installer4/workspace/Launch Environment Flexy/workdir/install-dir' level=info msg="Waiting up to 30m0s for the cluster at https://api.qeci-4052.qe.devcluster.openshift.com:6443 to initialize..." level=info msg="Cluster operator insights Disabled is False with : " level=fatal msg="failed to initialize the cluster: Could not update deployment \"openshift-cloud-credential-operator/cloud-credential-operator\" (176 of 569)" flexy job: https://openshift-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Launch%20Environment%20Flexy/88600/ From cvo log, also found similar logs: I0410 09:25:03.670199 1 cvo.go:439] Started syncing cluster version "openshift-cluster-version/version" (2020-04-10 09:25:03.670188248 +0000 UTC m=+227.395008648) I0410 09:25:03.670334 1 cvo.go:471] Desired version from operator is v1.Update{Version:"4.5.0-0.nightly-2020-04-10-040610", Image:"registry.svc.ci.openshift.org/ocp/release@sha256:346bb1af026178aa71d5e299f8c8dd3465f98855628be9caae45b0976bb13cf3", Force:false} I0410 09:25:03.670437 1 cvo.go:441] Finished syncing cluster version "openshift-cluster-version/version" (245.452µs) E0410 09:25:06.822038 1 task.go:81] error running apply for deployment "openshift-cloud-credential-operator/cloud-credential-operator" (176 of 569): requested injection for non-existent container: "manager" Version: 4.5.0-0.nightly-2020-04-10-040610 How reproducible: Steps to Reproduce: 1. CI job is failed with above error 2. Rebuild flexy job to install ocp again, issue is reproduced. 3. Installation is failed when wait-for install-complete Actual results: ocp installation is failed. Expected results: ocp should be installed successfully. Additional info:
Verify the bug to install ocp with night build: 4.5.0-0.nightly-2020-04-14-002513, and passed.
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