This fix contains the following changes coming from updated version of kubernetes up to v1.24.6: Changelog: v1.24.6: https://github.com/kubernetes/kubernetes/blob/release-1.24/CHANGELOG/CHANGELOG-1.24.md#changelog-since-v1245 v1.24.5: https://github.com/kubernetes/kubernetes/blob/release-1.24/CHANGELOG/CHANGELOG-1.24.md#changelog-since-v1244 v1.24.4: https://github.com/kubernetes/kubernetes/blob/release-1.24/CHANGELOG/CHANGELOG-1.24.md#changelog-since-v1243 v1.24.3: https://github.com/kubernetes/kubernetes/blob/release-1.24/CHANGELOG/CHANGELOG-1.24.md#changelog-since-v1242 v1.24.2: https://github.com/kubernetes/kubernetes/blob/release-1.24/CHANGELOG/CHANGELOG-1.24.md#changelog-since-v1241 v1.24.1: https://github.com/kubernetes/kubernetes/blob/release-1.24/CHANGELOG/CHANGELOG-1.24.md#changelog-since-v1240
Verification steps: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-10-19-012002 True False 18m Cluster version is 4.11.0-0.nightly-2022-10-19-012002 Check the kubelet version as below, $ oc get no NAME STATUS ROLES AGE VERSION ip-10-0-xxx-225.us-west-2.compute.internal Ready worker 24m v1.24.6+5157800 ip-10-0-xxx-246.us-west-2.compute.internal Ready master 33m v1.24.6+5157800 ip-10-0-xxx-1.us-west-2.compute.internal Ready worker 27m v1.24.6+5157800 ip-10-0-xxx-179.us-west-2.compute.internal Ready master 33m v1.24.6+5157800 ip-10-0-xxx-20.us-west-2.compute.internal Ready master 33m v1.24.6+5157800 ip-10-0-xxx-184.us-west-2.compute.internal Ready worker 24m v1.24.6+5157800 Check the kube-apiserer version as below, $ oc get co/kube-apiserver -o yaml | grep -A1 '\- name: kube-apiserver' - name: kube-apiserver version: 1.24.6 Check Kubernetes version as below, $ oc version Client Version: 4.10.25 Server Version: 4.11.0-0.nightly-2022-10-19-012002 Kubernetes Version: v1.24.6+5157800 See above, Kubernetes is updated to 1.24.6. 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 (Important: OpenShift Container Platform 4.11.12 security 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/RHSA-2022:7201