Hide Forgot
The test has since been disabled (I will re-enable it separately), but the version SHA in the OLM binary appears to be incorrect again. See https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.6/1306079390244802560 as an example. It is referring to a commit that does not exist. This is reminiscent of https://bugzilla.redhat.com/show_bug.cgi?id=1873113
I rebuilt the 1.14 golang-builder with older tooling which regressed it (returned to setting environment vars it should not). It's been rebuilt and resynced, possibly OLM itself may need a rebuild but I expect this is fixed.
Cluster version is 4.6.0-0.nightly-2020-09-26-202331 [root@preserve-olm-env data]# oc -n openshift-operator-lifecycle-manager exec catalog-operator-55d7c54dd-588rw -- olm --version OLM version: 0.16.1 git commit: be18debfbb25ba768921373d48aa761b951eca59 I can find the commit on the master branch: https://github.com/operator-framework/operator-lifecycle-manager/commits/master LGTM, verify it.
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 (OpenShift Container Platform 4.6 GA Images), 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:4196