Epic Goal

• Support AIDE0.18 on FIO

Why is this important?

• AIDE 0.18.0 will be included with RHEL 10 next year. We must prepare for this migration since several options have been deprecated and removed in AIDE 0.18.0. it's crucial to develop migration logic before moving to AIDE 0.18.0 to ensure both default and user-provided aide configurations work seamlessly.

Acceptance Criteria

• Migration Logic Development
  • Be able to migrate the AIDE 0.16 config to the AIDE 0.18 config upstream.

• • Ensure configurations with unknown or incompatible parameters are flagged with a clear error message.
• End-to-End CI Implementation
  • Implement a full end-to-end CI using AIDE 0.18.0 to run checks against the migrated AIDE config.
  • Ensure e2e migration tests pass, including tests for upgrading configurations and databases.

• Final Migration PR
  • Have the final migration PR ready and waiting in review until we’re ready to start building FIO on UBI 10 or RHEL 10, which should have AIDE 0.18.0 by default.

• Documentation
  • Provide necessary details and documents on the migration and how to handle manual migration in case auto-migration fails.{}

Dependencies (internal and external)

1. Build FIO container with AIDE-0.18
2. Step FIO CI that runs AIDE-0.18
3. Downstream container builds with AIDE-0.18
4. RHEL 10 UBI image release downstream (External)

Aide Migration Plan

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>