Bug 1837958 - oc client downloaded from console display client version incorrectly
Summary: oc client downloaded from console display client version incorrectly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-20 09:35 UTC by XiaochuanWang
Modified: 2020-08-25 00:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 14:32:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description XiaochuanWang 2020-05-20 09:35:00 UTC 
Description of problem:
Download oc client and check client version, it display incorrectly.

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-05-19-041951

How reproducible:
Always

Steps to Reproduce:
1. Download oc client from web-console
2. Unzip client and check $ oc version
Client Version: 67da73a6d
Server Version: 4.5.0-0.nightly-2020-05-19-041951
Kubernetes Version: v1.18.2


Actual results:
Client Version: 67da73a6d

Expected results:
Correct version such as:
Client Version: 4.5.0-202005180117-d24a842

Additional info:
Comment 1 Jakub Hadvig 2020-05-20 11:00:15 UTC 
To clarify, the issue is that the version is incorrect? or its displayed incorrectly?
Comment 2 bpeterse 2020-05-20 13:54:36 UTC 
Passing this to oc.  We don't control the binary downloaded, just the deployment.
Comment 3 Maciej Szulik 2020-05-20 14:32:06 UTC 
This will contain the version from the binary that was uploaded to that URL where console points to.
If you use a proper oc binary from either a release payload or from an rpm it should be fine.
Note You need to log in before you can comment on or make changes to this bug.