Bug 1837958

Summary:	oc client downloaded from console display client version incorrectly
Product:	OpenShift Container Platform	Reporter:	XiaochuanWang <xiaocwan>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED NOTABUG	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	aos-bugs, jhadvig, jokerman, mfojtik
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 14:32:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.