Bug 2009018 - [4.9.z] legacy RHCOS boot image metadata is not in sync with stream metadata
Summary: [4.9.z] legacy RHCOS boot image metadata is not in sync with stream metadata
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.9.z
Assignee: Micah Abbott
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On: 2009000
Blocks: 2009019
TreeView+ depends on / blocked
 
Reported: 2021-09-29 17:30 UTC by Micah Abbott
Modified: 2021-09-29 17:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2009000
: 2009019 (view as bug list)
Environment:
Last Closed: 2021-09-29 17:30:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Micah Abbott 2021-09-29 17:30:12 UTC
This BZ is created to facilitate the fix in 4.8.z; this problem does not actually affect 4.9.z

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

When the most recent RHCOS boot image bump for 4.8 landed, only the stream metadata was changed. This was done since `openshift-installer` itself was updated to use only the stream metadata.

https://github.com/openshift/installer/pull/5227

However, it appears that UPI jobs still rely on the "legacy" metadata:

https://github.com/openshift/installer/blob/release-4.8/images/installer/Dockerfile.upi.ci#L17


While the drift in the different metadata sources shouldn't break the UPI jobs, it creates a different workflow as the IPI jobs will start from a different set of RHCOS artifacts than the UPI jobs.

--- Additional comment from Micah Abbott on 2021-09-29 16:34:34 UTC ---

@gpei noticed this discrepancy first - https://github.com/openshift/installer/pull/5227#issuecomment-930010185

--- Additional comment from Micah Abbott on 2021-09-29 17:25:46 UTC ---

This issue only affects 4.8 and will be used as the source for the necessary backport BZs.

Closing as CURRENTRELEASE


Note You need to log in before you can comment on or make changes to this bug.