-
Epic
-
Resolution: Done
-
Blocker
-
None
-
File Integrity Operator RHEL-9 support
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
Approved
Epic Goal
- Support RHEL-9 cluster nodes
Why is this important?
- OCP is transitioning to RHEL-9 and because FIO mounts the host FS, stores data there etc we need to make sure it keeps working
Scenarios
- As an OCP admin, I want to upgrade from OCP version based on RHEL-8 to an OCP version based on RHEL-9 while keeping FIO working. A large number (all?) files are expected to change during the upgrade.
- As an OCP admin, I want to install a fresh OCP cluster based on RHEL-9 and watch its file integrity
Acceptance Criteria
- FIO must support both RHEL-8 and RHEL-9 during the transition period
- Ideally we should test both RHEL-9 and RHEL-8 based clusters in CI, not sure if that's feasible
Dependencies (internal and external)
- OCP must be installable with RHEL-9 for us to be able to test the operator
Previous Work (Optional):
- The CaC team has been busy working on RHEL-9 STIG draft. Chances are they tested AIDE on RHEL-9 at least standalone.
Open questions::
- Do we need to rebuild the aide container atop RHEL-9 or even keep both as long as OCP supports both RHEL-8 and RHEL-9? I don't think so, but worth keeping in mind
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>
- clones
-
CMP-1343 RHEL-9 support in compliance operator and content
- Closed
There are no Sub-Tasks for this issue.