Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1873113

Summary: payload promotion stuck because build commit is not correct
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: Test InfrastructureAssignee: Justin Pierce <jupierce>
Status: CLOSED UPSTREAM QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.6CC: aos-bugs, jokerman, jupierce, mifiedle, wking, xiuwang
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-06 12:31:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Eads 2020-08-27 12:15:21 UTC 
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.
Comment 1 David Eads 2020-08-27 13:05:13 UTC 
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.
Comment 2 W. Trevor King 2020-08-27 18:10:53 UTC 
Example job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.6/1299012851003822080
Comment 3 David Eads 2020-08-27 18:29:01 UTC 
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.
Comment 12 Mike Fiedler 2020-11-06 12:31:09 UTC 
Marking closed -> upstream.  Not a valid QA bug