Bug 1767771 - [UPI][BAREMETAL] RHCOS 4.2 installation does not work when using bonding configuration
Summary: [UPI][BAREMETAL] RHCOS 4.2 installation does not work when using bonding conf...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.z
Assignee: Vadim Rutkovsky
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On: 1758091
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-01 11:46 UTC by Vadim Rutkovsky
Modified: 2023-09-07 20:54 UTC (History)
32 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1758091
Environment:
Last Closed: 2020-02-12 19:51:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Micah Abbott 2019-11-07 19:42:55 UTC 
Once the 4.3 BZ is verified, the fixed ignition RPM will need to be correctly tagged for 4.2.
Comment 3 Micah Abbott 2019-11-13 15:45:54 UTC 
@vadim Could you backport the fix for this into a 4.2 build of Ignition?
Comment 6 Micah Abbott 2019-12-04 18:32:31 UTC 
Backport to 4.2 merged, fix should be available in `ignition-0.33.0-7.rhaos4.2.gitc65e95c.el8`

We'll need to coordinate how to produce updated boot images for this fix to be fully delivered.
Comment 11 Micah Abbott 2019-12-12 14:38:33 UTC 
There is an updated version of Ignition (ignition-0.33.0-7.rhaos4.2.gitc65e95c.el8) for 4.2.z that has the necessary fix for this BZ.  However, since Ignition is a first-boot only service, the way to deliver this fix is through updated boot images.  Simply shipping an `machine-os-content` will not be sufficient.

The decision was made early on in the OCP 4 program to only ship `machine-os-content` for z-stream releases.  However, in this case, we truly need the updated boot images in order to consider this BZ fixed.

Discussions have been started on how best to deliver these updated boot images (since we've never had to do this before), so until the details are sorted out I'm going to move this BZ to POST until the boot images are ready to ship.
Comment 22 Micah Abbott 2020-02-12 19:51:13 UTC 
4.2.17 ended up getting skipped.  

However, 4.2.18 was released yesterday (Feb 11) - https://access.redhat.com/errata/RHBA-2020:0394

The updated boot media that includes the necessary fixes can be found on mirror.openshift.com:

https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.2/4.2.18/

I neglected to correctly attach this BZ to the errata, but will move this BZ to CLOSED/CURRENTRELEASE
Note You need to log in before you can comment on or make changes to this bug.