Epic Goal

• Provide a dynamically-linked build of the installer for RHEL 9 in the release payload

Why is this important?

• RHEL 9 is out and users are switching to it
• When the host is in FIPS mode, a dynamically-linked build of the installer is required
• RHEL 8 & 9 have different versions of OpenSSL, so there's no one build that can work on both.

Scenarios

1. Installing a FIPS mode cluster with the installer running on RHEL 9 with FIPS enabled
2. Installing a baremetal IPI cluster with the installer running on RHEL 9

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ART-7207

Open questions::

1. Do we need to build for both RHEL 8 & RHEL 9, or could we just switch the build to RHEL 9 at this point?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>