Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1783056

Summary:	RHCoS should report a version number to the change log so that we can debug problems
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	RHCOS	Assignee:	Micah Abbott <miabbott>
Status:	CLOSED WONTFIX	QA Contact:	Michael Nguyen <mnguyen>
Severity:	high	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	bbreard, dustymabe, imcleod, jligon, miabbott, mnguyen, nstielau, smilner
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1783055	Environment:
Last Closed:	2021-01-04 15:28:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1783055
Bug Blocks:

Description Clayton Coleman 2019-12-12 22:17:08 UTC

+++ This bug was initially created as a clone of Bug #1783055 +++

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.versions="machine-os=SEMVER"
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.

--- Additional comment from Clayton Coleman on 2019-12-12 17:15:12 EST ---

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?)

Comment 6 Micah Abbott 2020-06-16 19:04:15 UTC

Higher priority items prevented this BZ from being worked on and it is unclear how desirable this fix would be for 4.3.z

Lowering priority to 'low' and marking for UpcomingSprint

Comment 7 Micah Abbott 2020-07-08 18:29:04 UTC

Higher priority items prevented this BZ from being worked on and it is unclear how desirable this fix would be for 4.3.z.  Marking for UpcomingSprint.

Comment 8 Micah Abbott 2020-07-15 13:01:10 UTC

Will investigate the feasibility of backporting the necessary changes to enable this during this sprint.

Comment 9 Micah Abbott 2020-08-05 20:12:08 UTC

As 4.3 is getting close to EOL, it's unlikely we will backport the various changes needed to enable this request.  It is a nice to have (and one that I had wished for in 4.3 recently), but we have higher priority tasks in front of us.  

Additionally, this functionality has been enabled in 4.4 and beyond, so future releases will be covered.

Comment 10 Micah Abbott 2021-01-04 15:28:06 UTC

Not sure why this was reopened by the bot without any context; closing as WONTFIX again.