The hyperkube binary is used to launch the kubelet on the node and reports back its version number to the cluster as part of the Node object. We need the commit reported to match a real commit accessible in the openshift/origin and openshift/ose history so that we can identify which code is in use.
The rpm build script when involved by ART jobs should ensure that the commit reported by hyperkube and the RPM version label should match a real, reachable OSE commit.
Luke confirmed this is still an issue post-incremental, tracking here so we don't forget. Does not block beta3
This *should* be correct now. It should be evident once we actually get a 4.1 payload.
Verified on 4.1.0-0.nightly-2019-05-03-093152
From the Node:
Verified this matches the commit in OSE
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.