Hide Forgot
This fix contains the following changes coming from updated version of kubernetes up to v1.23.10: Changelog: v1.23.12: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v12311 v1.23.12: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v12310 v1.23.10: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v1239 v1.23.9: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v1238 v1.23.8: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v1237 v1.23.7: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v1236 v1.23.6: https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#changelog-since-v1235
Verification steps: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-10-17-082154 True False 142m Cluster version is 4.10.0-0.nightly-2022-10-17-082154 Check the kubelet version as below, $ oc get no NAME STATUS ROLES AGE VERSION kewang-2010vs1-jprqg-master-0 Ready master 164m v1.23.12+6b34f32 kewang-2010vs1-jprqg-master-1 Ready master 164m v1.23.12+6b34f32 kewang-2010vs1-jprqg-master-2 Ready master 164m v1.23.12+6b34f32 kewang-2010vs1-jprqg-worker-lmcwx Ready worker 155m v1.23.12+6b34f32 kewang-2010vs1-jprqg-worker-mcvjk Ready worker 155m v1.23.12+6b34f32 Check the kube-apiserer version as below, $ oc get co/kube-apiserver -o yaml | grep -A1 '\- name: kube-apiserver' - name: kube-apiserver version: 1.23.12 Check Kubernetes version as below, $ oc version Client Version: 4.12.0-0.nightly-2022-09-01-225012 Kustomize Version: v4.5.4 Server Version: 4.10.0-0.nightly-2022-10-17-082154 Kubernetes Version: v1.23.12+6b34f32 See above, Kubernetes is updated to 1.23.12. 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.38 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-2022:7035