Epic Goal

• Support MicroShift 4.14 and 4.15 on RHEL 9.3.

Why is this important?

• Customers need access to newer RHEL for hardware enablement.

Scenarios

1. Standard test scenarios on RHEL 9.3.
2. Upgrade test scenarios on RHEL 9.3 (upgrading MicroShift in place on 9.3)
3. Standard test scenarios on unbounded RHEL (to catch future OS issues).
4. Test updating only the OS from RHEL 9.2 to 9.3 (using the same version of MicroShift eliminates MicroShift as a source of issues).
5. Test updating from main on RHEL 9.2 to PR on RHEL 9.3 (gives us 1 upgrade job with MicroShift changing as well as RHEL).

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.  MicroShift & RHEL Combinations Support Policy

Open questions::

1. ...

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>