Epic Goal

• New installs of OMR and upgrades of existing installations are automatically updated to use an up to date version of a supported database.

Why is this important?

• Postgres 10 is going EOL inside Red Hat in May 2024.
• OMR uses Postgres 10 and there is no built in logic for updating
• If we don't update OMR to use an updated database, customers will be stuck with an unsupported database

Scenarios

1. New installs of OMR include and configure a supported database
2. Upgraded installs of OMR automatically update the existing database
3. A Backup of the Postgres db is taken and can be restored in the event of a failed upgrade

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Docs/release notes have been updated

Dependencies (internal and external)

1. RHEL 9.1 or above

Previous Work (Optional):

1. https://issues.redhat.com/browse/PROJQUAY-4608

Open questions::

1. How much additional space should we tell customers they need for the db backup?

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>