We have repeatedly struggled to map payload to RHCoS version to list of RHCoS changes, which hampered debugging efforts and wastes time.
We need to report RHCoS component version in the payload (like Kubernetes) by:
1. Report a version in the machine-os-content image from the coreos pipelines:
LABEL io.openshift.build.version-display-name="machine-os=RHEL CoreOS"
2. Ideally make that SEMVER be the same version listed in rhcos build output results so we don't have to translate it
3. Update the release tooling to support display name (we can't use "machine os" and we need to distinguish between fedora and rhcos)
4. Update the release controller to direct link to the appropriate details page for an rhcos version
This will allow both dev and QE to more rapidly understand what is happening in CI.
This is not required for 4.3.0 but may not be changeable in z. I'd prefer to get it in 4.3.0 esp. if it causes minor tooling issues later.
As a consequence of this change an engineer or qe or manager could one click from openshift-release.svc.ci.openshift.org directly to the list of changes, and when we do diffs we could link new and old (I believe the viewer page supports diffs?)
Verified labels are in 4.4.0-0.nightly-2020-03-11-062559
$ oc image -a ../all-the-pull-secrets.json info $(oc adm release -a ../all-the-pull-secrets.json info --image-for machine-os-content registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-03-11-062559)
Media Type: application/vnd.docker.distribution.manifest.v2+json
Created: 20h ago
Image Size: 801MB
io.openshift.build.version-display-names=machine-os=Red Hat Enterprise Linux CoreOS
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.