This was caught by `[sig-operator] OLM should [Serial] olm version should contain the source commit id [Suite:openshift/conformance/serial]` Which failed on fail [github.com/openshift/origin@/test/extended/operators/olm.go:141]: Aug 27 10:02:47.353: Git.GetCommit returned error: GET https://api.github.com/repos/operator-framework/operator-lifecycle-manager/git/commits/0b366669d0b49e96751a00330c9dea70b8c36b83: 404 Not Found [] However, the commit itself doesn't exist in the https://github.com/operator-framework/operator-lifecycle-manager repo, so the going theory is that somewhere the build process placed an incorrect commit into the binary.
I think it's more likely that something in the build pipeline is broken than that OLM messed up their version in code. Reassigning to ART/release.
Example job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.6/1299012851003822080
looking https://testgrid.k8s.io/redhat-openshift-ocp-release-4.6-blocking#release-openshift-ocp-installer-e2e-aws-serial-4.6 which does not have this problem, we can see that grep -r 'kube-controller-manager-operator version' '/home/deads/Downloads/working-must-gather' builder.go:238] kube-controller-manager-operator version v0.0.0-alpha.0-807-g4ff72a19-4ff72a19d344ce2bf09fa597e44d14a77a5a93ed grep -r 'openshift-kube-storage-version-migrator-operator version' '/home/deads/Downloads/working-must-gather' builder.go:223] openshift-kube-storage-version-migrator-operator version 25cd565-25cd56524362d1104158e54d2828ee3e81688332 these SHAs correspond to commits in the source repos. source: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-serial-4.6/1299011038250799104 looking at a failing test for promotion https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.6/1299012851003822080 and running the same greps grep -r 'kube-controller-manager-operator version' '/home/deads/Downloads/broke-serial-must-gather' builder.go:238] kube-controller-manager-operator version 0b36666-0b366669d0b49e96751a00330c9dea70b8c36b83 grep -r 'openshift-kube-storage-version-migrator-operator version' '/home/deads/Downloads/broke-serial-must-gather' builder.go:223] openshift-kube-storage-version-migrator-operator version 0b36666-0b366669d0b49e96751a00330c9dea70b8c36b83 Notice that the failing build has a different format and lists what appears to be a SHA that is the *same* for both repos (this doesn't happen) and notice that sha is the same as OLM.
Marking closed -> upstream. Not a valid QA bug