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

Bug 1862042

Summary: `oc version` and `oc get node` show Kubernetes Version incorrectly
Product: OpenShift Container Platform Reporter: zhou ying <yinzhou>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED DUPLICATE QA Contact: Ke Wang <kewang>
Severity: medium Docs Contact:
Priority: low    
Version: 4.6CC: aos-bugs, dshchedr, jmencak, jokerman, mfojtik, sjenning, xxia
Target Milestone: ---Flags: mfojtik: needinfo?
Target Release: 4.6.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: 2020-09-07 07:24:55 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 zhou ying 2020-07-30 09:33:35 UTC
Description of problem:
`oc version` and `oc get node` show Kubernetes Version incorrectly

Version-Release number of selected component (if applicable):
[root@dhcp-140-138 ~]# oc version
Client Version: 4.6.0-202007290214.p0-0180b33
Server Version: 4.6.0-0.nightly-2020-07-29-214846
Kubernetes Version: v4.6.0-202007282157.p0-dirty


How reproducible:
always

Steps to Reproduce:
1) Create cluster with payload: 4.6.0-0.nightly-2020-07-29-214846
2) Check `oc version`
3) `oc get node`

Actual results:
2. Show the "Kubernetes Version" incorrectly:
Client Version: 4.6.0-202007290214.p0-0180b33
Server Version: 4.6.0-0.nightly-2020-07-25-091217
Kubernetes Version: v4.6.0-202007250017.p0-dirty
3. show v0.0.0-master+$Format:%h$:
xxia0730b-cgb8n-master-0       Ready    master   123m   v0.0.0-master+$Format:%h$

Expected results:
Show the "Kubernetes Version" and node version correctly

Additional info:

Comment 1 Mrunal Patel 2020-08-07 00:11:04 UTC
*** Bug 1863330 has been marked as a duplicate of this bug. ***

Comment 2 Seth Jennings 2020-08-07 21:19:53 UTC
This could be a side effect of moving the hyperkube build from openshift/origin to openshift/kubernetes.

Comment 3 Michal Fojtik 2020-09-06 22:18:11 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 Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 4 Ke Wang 2020-09-07 07:24:55 UTC
This bug has some overlap with bug 1867499, there is no this problem in latest OCP payload.

$ oc version -o yaml
clientVersion:
  buildDate: "2020-09-04T06:40:10Z"
  compiler: gc
  gitCommit: f2a4a0375cc7b0eacb5467a0214303983e1151d6
  gitTreeState: clean
  gitVersion: 4.6.0-202009040605.p0-f2a4a03
  goVersion: go1.14.4
  major: ""
  minor: ""
  platform: linux/amd64
openshiftVersion: 4.6.0-0.nightly-2020-09-05-015624
serverVersion:
  buildDate: "2020-09-04T01:56:40Z"
  compiler: gc
  gitCommit: 068702de7d48739e835ea41b7ca959b5252de432
  gitTreeState: clean
  gitVersion: v1.19.0-rc.2+068702d
  goVersion: go1.14.4
  major: "1"
  minor: 19+
  platform: linux/amd64

$ oc get nodes
NAME                                        STATUS   ROLES    AGE    VERSION
ip-10-0-48-217.us-east-2.compute.internal   Ready    master   3h8m   v1.19.0-rc.2+068702d
ip-10-0-53-74.us-east-2.compute.internal    Ready    worker   172m   v1.19.0-rc.2+068702d
ip-10-0-54-83.us-east-2.compute.internal    Ready    worker   172m   v1.19.0-rc.2+068702d
ip-10-0-55-24.us-east-2.compute.internal    Ready    master   3h8m   v1.19.0-rc.2+068702d
ip-10-0-74-143.us-east-2.compute.internal   Ready    worker   172m   v1.19.0-rc.2+068702d
ip-10-0-78-5.us-east-2.compute.internal     Ready    master   3h8m   v1.19.0-rc.2+068702d

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