This is a tracker for https://bugzilla.redhat.com/show_bug.cgi?id=2011513 which links to https://github.com/openshift/kubernetes/pull/1007 which merged with commit `9312243` https://github.com/openshift/kubernetes/commit/931224322c58da67eb8b3e9d4d3ff0e7dbf81cf2 The latest RHCOS 4.10 build (410.84.202110081440-0) includes `openshift-hyperkube-4.10.0-202110080521.p0.git.9312243.assembly.stream.el8` The NVR of that `openshift-hyperkube` build points to commit `9312243` which is the commit containing the fix for BZ#2011513 A quick test on a single RHCOS node shows that the `kubelet` is at the version as expected: ``` [core@cosa-devsh ~]$ rpm-ostree status State: idle Deployments: * ostree://67be3786510771cc550aa4be162f2b45cb796e4340755d7a67fa4720aa10e9ba Version: 410.84.202110081440-0 (2021-10-08T14:43:28Z) [core@cosa-devsh ~]$ rpm -q openshift-hyperkube openshift-hyperkube-4.10.0-202110080521.p0.git.9312243.assembly.stream.el8.x86_64 [core@cosa-devsh ~]$ kubelet --version Kubernetes v1.22.1+9312243 ``` Marking this as `Verified: Tested` to indicate that the fixed version of the `kubelet` is present in the RHCOS build.
This bug has been reported fixed in a new RHCOS build and is ready for QE verification. To mark the bug verified, set the Verified field to Tested. This bug will automatically move to MODIFIED once the fix has landed in a new bootimage.
The fix for this bug has landed in a bootimage bump, as tracked in bug 2004596 (now in status MODIFIED). Moving this bug to MODIFIED.
Moving to verified now that the boot image bump has been verified here https://bugzilla.redhat.com/show_bug.cgi?id=2004596
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 (Moderate: OpenShift Container Platform 4.10.3 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:0056