Description of problem: The RHCOS image and osImages for 4.6 rc's have a week old version of hyperkube in them Version-Release number of selected component (if applicable): 4.6.0-rc1 How reproducible: Always Steps to Reproduce: 1. Install cluster and get kubelet version as v1.19.0+db1fc96 which is from 1w ago https://github.com/openshift/kubernetes/commit/db1fc96 Actual results: Old hyperkube Expected results: hyperkube built from latest o/k release-4.6 Additional info:
Bug requested by Eric for tracking release blocking situation
Builds are in process by ART as of around 50 minutes ago.
Fortunately, David made the only PR that is missing $ git log --oneline --no-merges db1fc96..openshift/release-4.6 d339db6dbb3 UPSTREAM: 95364: set lastterminationstate for container status even when CRI fails to return termination (or any) data
Updated package is available in 4.6.0-0.nightly-2020-10-09-153352 (46.82.202010081751-0) roughly as of Friday late afternoon. The same for CI builds. There were two package updates on Friday: - 4.6.0-202010081244.p0.git.94033.c107fa2.el8 - 4.6.0-202010081843.p0.git.94035.af27205.el8 Marking 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.6 GA Images), 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-2020:4196