Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
For Databases, upgrade of the OS is always a sensitive event, and in many cases the major version of the database server is changed.

The upgrade should be more described in a Migration guide and/or a KB article.

When the system looks like it includes an initialized database, the LEAPP tool should warn users ahead about possible issues during the upgrade, the need of a proper backup, and ideally at least point to that documentation, 

This bug is supposed to track the work on creating such a LEAPP actor that would help database users before the upgrade itself.

Before there is some more concrete documentation, the doc for 7 to 8 migration might be used:
https://leapp.readthedocs.io/en/latest/el7toel8/actor-rhel7-to-rhel8.html

We're currently looking for something similar to the PostgreSQL actor for helping with 7 to 8 migration:
https://github.com/oamg/leapp-repository/blob/c4e6a10cb78f6cdd08b89f0ad938576d8ecbf28f/repos/system_upgrade/el7toel8/actors/postgresqlcheck/libraries/postgresqlcheck.py

But in this case for 8->9 migration and for MySQL component.

There is already some pre-work done but not finished:
https://github.com/oamg/leapp-repository/pull/510

PR: https://github.com/oamg/leapp-repository/pull/836

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.