This fix contains the following changes coming from updated version of kubernetes from 1.23.3 up to v1.23.5:
Changelog for v1.23.5:
Changelog for v1.23.4:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.10.0-0.nightly-2022-03-22-030457 True False 26m Cluster version is 4.10.0-0.nightly-2022-03-22-030457
Checking the kubelet version on nodes and kube-apiserver version,
$ oc get no
NAME STATUS ROLES AGE VERSION
ip-10-0-140-46.us-east-2.compute.internal Ready master 49m v1.23.5+b0357ed
ip-10-0-149-70.us-east-2.compute.internal Ready worker 42m v1.23.5+b0357ed
ip-10-0-185-95.us-east-2.compute.internal Ready worker 36m v1.23.5+b0357ed
ip-10-0-190-31.us-east-2.compute.internal Ready master 48m v1.23.5+b0357ed
ip-10-0-193-235.us-east-2.compute.internal Ready master 49m v1.23.5+b0357ed
$ oc get co/kube-apiserver -o yaml | grep -A1 '\- name: kube-apiserver'
- name: kube-apiserver
$ oc version
Client Version: 4.10.0-0.nightly-2022-03-19-230512
Server Version: 4.10.0-0.nightly-2022-03-22-030457
Kubernetes Version: v1.23.5+b0357ed
See above, Kubernetes is updated to 1.23.5. 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.
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.10.6 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.