-
Bug
-
Resolution: Unresolved
-
Normal
-
4.21.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Analysis
Timeline Comparison:
| Date | Event |
|--------------|-------------------------------------------------------------------------|
| Oct 21, 2025 | PR #7032 merged to main (commit 440fc1127) - ADDED hypershift-no-cgo |
| Oct 30, 2025 | quay.io/hypershift/hypershift-operator:latest built (revision 60d587d1) |
The :latest image was built 9 days AFTER PR #7032 was merged, yet it DOES NOT contain hypershift-no-cgo.
Why is hypershift-no-cgo Missing?
Root Cause: The image was built from commit 60d587d1286655c5e777e63959aaae224123ea95, which:
1. Not in the upstream repo: This commit is not accessible from the public GitHub repository
fatal: remote error: upload-pack: not our ref 60d587d1286655c5e777e63959aaae224123ea95
2. Likely from a different branch/fork: Possible sources:
- A release branch that hasn't backported PR #7032
- An internal/private branch used for CI builds
- A conflux/staging branch
- A forked repository
3. Built with OLD Containerfile: The revision 60d587d1 predates or doesn't include PR #7032, so the Containerfile used was:
# OLD (before PR #7032)
RUN make hypershift \ # ← No hypershift-no-cgo
&& make hypershift-operator \
&& make product-cli \
&& make karpenter-operator
COPY --from=builder /hypershift/bin/hypershift \ # ← No hypershift-no-cgo
/hypershift/bin/hcp \
/hypershift/bin/hypershift-operator \
/hypershift/bin/karpenter-operator \
/usr/bin/
---
Implications for Your CI
CRITICAL: Your CI is hitting this exact issue:
1. Current Situation:
- CI extracts /usr/bin/hypershift from quay.io/hypershift/hypershift-operator:latest
- This binary is from PRE-PR#7032 (statically linked, no FIPS)
- Wait, this contradicts your error message!
🚨 WAIT - CONTRADICTION DETECTED!
Your original error was:
hypershift: /lib64/libc.so.6: version `GLIBC_2.32' not found
hypershift: /lib64/libc.so.6: version `GLIBC_2.34' not found
This error means the binary IS dynamically linked (requires GLIBC), which suggests it WAS built with CGO enabled.
But if the image doesn't have hypershift-no-cgo, it should be from before PR #7032, which means it should be statically linked and NOT require GLIBC!
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Run hypershift install job https://jenkins-csb-openshift-qe-mastern.dno.corp.redhat.com/job/ocp-common/job/Flexy-install/360716/console
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-63049 Make the hypershift CLI binary FIPS compliant
-
- Verified
-
- links to