Bug 1848731

Summary:	RFE: Test migration scenarios for mariadb and mysql
Product:	Red Hat Enterprise Linux 8	Reporter:	Honza Horak <hhorak>
Component:	mariadb	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED WONTFIX	QA Contact:	Jakub Heger <jheger>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	databases-maint, hhorak, jheger, ljavorsk, zmiklank
Target Milestone:	rc	Keywords:	FutureFeature, Reopened, TestCaseNeeded, TestOnly, Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-27 07:27:35 UTC	Type:	Story
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 2020-06-18 20:30:16 UTC

Description of problem:

Similar to PostgreSQL (https://src.osci.redhat.com/tests/postgresql/blob/master/f/Sanity/pg_upgrade), we should make sure (i.e. have a test) that the upgrade scenarios work fine when users move between different streams.

We can also have pre-generated data in binary format to avoid need to run different versions of a database, but on the other hand it would be good to test the "replacing RPMs" step as well. Not sure how this can be done though.

Comment 9 RHEL Program Management 2022-01-26 07:27:10 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 18 RHEL Program Management 2022-07-27 07:27:35 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.