Bug 1987260 - Incorrect oc version in user-agent of oc client [NEEDINFO]
Summary: Incorrect oc version in user-agent of oc client
Keywords:
Status: CLOSED DUPLICATE of bug 1987257
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.8
Hardware: All
OS: All
low
medium
Target Milestone: ---
: ---
Assignee: Ross Peoples
QA Contact: zhou ying
URL:
Whiteboard: LifecycleStale
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-29 11:06 UTC by Timothy Rees
Modified: 2022-12-08 10:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-08 10:28:54 UTC
Target Upstream Version:
Embargoed:
mfojtik: needinfo?

Attachments (Terms of Use)

Description Timothy Rees 2021-07-29 11:06:44 UTC 
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

How reproducible:

100%

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
3.

Actual results:

User agent is "oc/4.8.0 (darwin/amd64) kubernetes/1077b05"

Expected results:

"oc/4.8.2 (darwin/amd64) kubernetes/1077b05"

I'm not sure what the kubernetes value should be.

Additional info:

There is a related bz for consistency with user-agent; https://bugzilla.redhat.com/show_bug.cgi?id=1987257
Comment 1 Maciej Szulik 2021-08-19 14:07:30 UTC 
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.
Comment 2 Michal Fojtik 2021-10-01 11:30:06 UTC 
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.
Comment 3 Michal Fojtik 2021-11-03 19:30:00 UTC 
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.
Comment 4 Michal Fojtik 2021-12-04 11:39:20 UTC 
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.
Comment 5 Michal Fojtik 2022-01-05 16:22:28 UTC 
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.
Comment 7 Michal Fojtik 2022-01-10 15:52:20 UTC 
The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.
Comment 8 Michal Fojtik 2022-02-09 16:39:36 UTC 
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.
Comment 9 Arda Guclu 2022-12-08 10:28:26 UTC 
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.
Comment 10 Arda Guclu 2022-12-08 10:28:54 UTC 

*** This bug has been marked as a duplicate of bug 1987257 ***
Note You need to log in before you can comment on or make changes to this bug.