Description of problem:
The oc-mirror version command outputs a git hash that customers cannot easily relate to an OpenShift verison like 4.19.7
Version-Release number of selected component (if applicable):
4.19.0-202507292137.p0.gaa8c685.assembly.stream.el9-aa8c685
How reproducible:
100%
Steps to Reproduce:
1.Run the command 'oc-mirror version'
Actual results:
W0826 10:14:44.377678 572874 mirror.go:86] ⚠️ oc-mirror v1 is deprecated (starting in 4.18 release) and will be removed in a future release - please migrate to oc-mirror --v2WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.19.0-202507292137.p0.gaa8c685.assembly.stream.el9-aa8c685", GitCommit:"aa8c68526ba4133f14bcc62da153ba1328cbcf1c", GitTreeState:"clean", BuildDate:"2025-07-29T23:04:40Z", GoVersion:"go1.23.9 (Red Hat 1.23.9-1.el9_6) X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}
Expected results:
Something like: 4.19.7
Additional info:
When there are challenges with mirroring content into a customer's environment we often start by understanding what version of the oc-mirror binary the customer is using on both the internet connected and disconnected side. The git hash makes it difficult for us to do that. Customers do not know how to map the git hash to an OCP release.
- is related to
-
CLID-428 Address feedback from NAPS Hackathon
-
- In Progress
-
- links to