Bug 1697213

Summary:	Node kubelet show k8s version as 1.12 while cluster show k8s version as 1.13
Product:	OpenShift Container Platform	Reporter:	Liang Xia <lxia>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED DUPLICATE	QA Contact:	Jianwei Hou <jhou>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, hongkliu, jokerman, mifiedle, mmccomas, sejug, walters
Target Milestone:	---
Target Release:	4.1.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-04-08 20:35:50 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 Liang Xia 2019-04-08 05:57:04 UTC

Description of problem:
Chcke cluster version and node kubelet version.
Cluster is running with kubernetes v1.13,
while node kubelet show the version is v1.12

Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-04-05-165550

How reproducible:
Always

Steps to Reproduce:
1.Check cluster version.
$ oc adm release info
2.Check node kubelet version
$ oc get nodes -o wide


Actual results:
$ oc get nodes -o wide
NAME                                              STATUS   ROLES    AGE    VERSION             INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                                                   KERNEL-VERSION         CONTAINER-RUNTIME
ip-172-31-137-255.eu-central-1.compute.internal   Ready    master   3h9m   v1.12.4+509916ce1   172.31.137.255   <none>        Red Hat Enterprise Linux CoreOS 410.8.20190329.0 (Ootpa)   4.18.0-80.el8.x86_64   cri-o://1.12.10-2.rhaos4.0.git2c94bb7.el7

$ oc adm release info
......
Component Versions:
  Kubernetes 1.13.4


Expected results:
Node kubelet should run k8s with version v1.13

Additional info:

Comment 2 Seth Jennings 2019-04-08 13:10:43 UTC

This is due to the lag with the RHCOS os-container image updating.  Should resolve on its own.  I'm upgrading my cluster now to see if the update has propagated.

Comment 3 Colin Walters 2019-04-08 15:42:35 UTC

This is blocked on https://bugzilla.redhat.com/show_bug.cgi?id=1696774

Comment 4 Seth Jennings 2019-04-08 20:35:50 UTC


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