Bug 2037851

Summary:	Create a Leapp actor for MySQL for RHEL 8->9 migration
Product:	Red Hat Enterprise Linux 9	Reporter:	Honza Horak <hhorak>
Component:	mysql	Assignee:	Michal Schorm <mschorm>
Status:	NEW ---	QA Contact:	RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	databases-maint, ljavorsk, lkuprova, pstodulk
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-06 07:28:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Honza Horak 2022-01-06 17:08:13 UTC

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.

Comment 2 RHEL Program Management 2023-07-06 07:28:06 UTC

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.

Comment 3 Petr Stodulka 2023-07-07 08:32:32 UTC

Reopenning to handle noisy autoclose.

Comment 4 Petr Stodulka 2023-07-07 08:32:49 UTC

Reopenning to handle noisy autoclose.