This fix contains the following changes coming from updated version of kubernetes up to v1.19.14: Changelog for v1.22.2: https://github.com/kubernetes/kubernetes/blob/release-1.22/CHANGELOG/CHANGELOG-1.22.md#changelog-since-v1221
Current PR bringing in kubernetes v1.22.2 is https://github.com/openshift/kubernetes/pull/985 This is bringing in the following changes: Changelog for v1.22.2: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.22.md#v1222
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-11-06-034743 True False 158m Cluster version is 4.9.0-0.nightly-2021-11-06-034743 $ oc get no NAME STATUS ROLES AGE VERSION kewang-08410g1-d6vrd-master-0.c.openshift-qe.internal Ready master 122m v1.22.1+d8c4430 kewang-08410g1-d6vrd-master-1.c.openshift-qe.internal Ready master 123m v1.22.1+d8c4430 kewang-08410g1-d6vrd-master-2.c.openshift-qe.internal Ready master 122m v1.22.1+d8c4430 kewang-08410g1-d6vrd-worker-a-lsgbm.c.openshift-qe.internal Ready worker 115m v1.22.1+d8c4430 kewang-08410g1-d6vrd-worker-b-q2dvr.c.openshift-qe.internal Ready worker 115m v1.22.1+d8c4430 $ oc get co/kube-apiserver -o yaml | grep -A1 '\- name: kube-apiserver' - name: kube-apiserver version: 1.22.2 See above, kubelet and kube-apiserver are updated to 1.22.2. As for functional tests, have to rely on QE's daily schedule regression tests. During the tests, if there will be issue hit on any component related to the rebase, separate bug should be filed. Move the bug VERIFIED.
Sorry, the kubelet still in 1.22.1, check Kubernetes as below, $ oc version Client Version: 4.10.0-0.nightly-2021-10-16-173656 Server Version: 4.9.0-0.nightly-2021-11-06-034743 Kubernetes Version: v1.22.2+efbddd0
The node version still not bumped to latest version 1.22.2 , assign this back: [root@localhost ~]# oc get node NAME STATUS ROLES AGE VERSION ip-10-0-132-203.us-east-2.compute.internal Ready master 45m v1.22.1+d8c4430 ip-10-0-134-58.us-east-2.compute.internal Ready worker 36m v1.22.1+d8c4430 ip-10-0-167-101.us-east-2.compute.internal Ready master 44m v1.22.1+d8c4430 ip-10-0-183-231.us-east-2.compute.internal Ready worker 36m v1.22.1+d8c4430 ip-10-0-200-142.us-east-2.compute.internal Ready master 45m v1.22.1+d8c4430 ip-10-0-200-247.us-east-2.compute.internal Ready worker 36m v1.22.1+d8c4430 [root@localhost ~]# oc version Client Version: 4.10.0-202110262029.p0.git.b241000.assembly.stream-b241000 Server Version: 4.9.7 Kubernetes Version: v1.22.2+5e38c72
Waiting for fix in CI https://github.com/openshift/kubernetes/pull/1044
A recent check, the kubelet has the same version v1.22.2 with Kubernetes, see below, # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-11-11-155043 True False 4h14m Cluster version is 4.9.0-0.nightly-2021-11-11-155043 # oc get node NAME STATUS ROLES AGE VERSION ip-10-0-136-28.us-east-2.compute.internal Ready worker 4h31m v1.22.2+5e38c72 ip-10-0-153-163.us-east-2.compute.internal Ready master 4h36m v1.22.2+5e38c72 ip-10-0-165-58.us-east-2.compute.internal Ready worker 4h31m v1.22.2+5e38c72 ip-10-0-166-67.us-east-2.compute.internal Ready master 4h36m v1.22.2+5e38c72 ip-10-0-201-175.us-east-2.compute.internal Ready master 4h36m v1.22.2+5e38c72 ip-10-0-211-114.us-east-2.compute.internal Ready worker 4h29m v1.22.2+5e38c72 # oc version Client Version: 4.9.0-0.nightly-2021-08-22-070405 Server Version: 4.9.0-0.nightly-2021-11-11-155043 Kubernetes Version: v1.22.2+5e38c72
Per Comment 14, move the bug VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.7 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:4579