Description of problem:
Incorrect oc version is displaying for the user-agent in the oc client.
I am using the 4.8.2 release of the client and the user-agent in quay.io logs when using oc adm mirror shows the user-agent to be 4.8.0; "oc/4.8.0 (darwin/amd64) kubernetes/1077b05"
Version-Release number of selected component (if applicable):
➜ tmp oc version
Client Version: 4.8.2
Steps to Reproduce:
1. Make request to registry, such as adm mirror to pull OCP4 core payload
2. Check registry logs and see the user-agent has the wrong version value
User agent is "oc/4.8.0 (darwin/amd64) kubernetes/1077b05"
"oc/4.8.2 (darwin/amd64) kubernetes/1077b05"
I'm not sure what the kubernetes value should be.
There is a related bz for consistency with user-agent; https://bugzilla.redhat.com/show_bug.cgi?id=1987257
Ross I did some initial changes in https://github.com/openshift/oc/pull/841 but Tim claims there's one more edge case not covered.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.
As far as I can see, this bug and this https://bugzilla.redhat.com/show_bug.cgi?id=1987257 looks same.
Since this https://bugzilla.redhat.com/show_bug.cgi?id=1987257 was already fixed. I'm closing this one.
Feel free re-open it if I'm missing something.
*** This bug has been marked as a duplicate of bug 1987257 ***