Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1781909

Summary: inconsitent prefix for oc get version output
Product: OpenShift Container Platform Reporter: Peter Ruan <pruan>
Component: ocAssignee: Maciej Szulik <maszulik>
Status: CLOSED DUPLICATE QA Contact: zhou ying <yinzhou>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, jokerman, mfojtik
Target Milestone: ---   
Target Release: 4.4.0   
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: 2019-12-11 16:23:31 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 Peter Ruan 2019-12-10 21:34:22 UTC 
Description of problem:
the output for `oc version` is inconsistent.  Some has the prefix `v` whille others have `openshift-clients-` 

For example:
pruan@desktop ~/Downloads/openshift-client-linux-4.3.0-0.nightly-2019-12-10-120829 $ ./oc version
Client Version: openshift-clients-4.3.0-201910250623-85-g3fa38ed2
Kubernetes Version: v1.11.0+d4cacc0
pruan@desktop ~/Downloads/openshift-client-linux-4.3.0-0.nightly-2019-12-10-120829 $ 
pruan@desktop ~/Downloads/openshift-client-linux-4.2.0-0.nightly-2019-12-10-130831 $ ./oc version
Client Version: openshift-clients-4.2.2-201910250432-8-g98a84c61
Kubernetes Version: v1.11.0+d4cacc0
#### 4.4 
pruan@desktop ~/Downloads/openshift-client-linux-4.4.0-0.ci-2019-12-09-231909 $ ./oc version
Client Version: v4.2.0-alpha.0-300-gec784bd
Kubernetes Version: v1.11.0+d4cacc0




Version-Release number of selected component (if applicable):

4.2, 4.3, 4.4 
How reproducible:

always
Steps to Reproduce:
1. download oc client and do oc version
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Maciej Szulik 2019-12-11 16:23:31 UTC 

*** This bug has been marked as a duplicate of bug 1780779 ***