Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test mariadb version upgrade #504

Open
dirkmueller opened this issue Jun 14, 2024 · 3 comments · May be fixed by #594
Open

Test mariadb version upgrade #504

dirkmueller opened this issue Jun 14, 2024 · 3 comments · May be fixed by #594
Assignees
@rcmadhankumar

Comments

@dirkmueller
Copy link
Member

Sle 15.5 to 15.6 is going to change the mariadb version and the docker entry point is handling version updates by going through a data migration workflow.

We do not have a test for that and we know the current state was broken because the upstream developers notified us about that issue.

We need to test an upgrade scenario
@dirkmueller dirkmueller mentioned this issue Jun 14, 2024
Open
@alexandrevicenzi
Copy link
Member

Is the test scenario in mind around mariadb-upgrade?

In theory, SLE is not going to move to a version where mariadb-upgrade would not work. If you follow the SLE upgrade paths, you can migrate from SLE 12 MariaDB to SLE 15 with no issues, as long as you always run mariadb-upgrade in each SLE migration.

@dirkmueller
Copy link
Member Author

@alexandrevicenzi the entrypoint script performs the upgrade itself based on some logic and extra code paths that were broken. we're not testing them. we should be testing them prior to playing out the 15.6 upgrade.

see docker_mariadb_upgrade in the entrypoint.sh

@grooverdan
Copy link

As your new entrypoint is fixed, I don't think you are in a bad position. The mariadb-upgrade checks the file $DATADIR/mariadb-upgrade-info ( or mysql_upgrade_info) for the version that was previously installed/upgraded. The old invalid version number in the entrypoint was only used as a pre-check comparison if an upgrade was needed and wasn't actually stored anywhere.

@rcmadhankumar rcmadhankumar linked a pull request Sep 13, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rcmadhankumar rcmadhankumar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Mariadb upgrade scenario testing SUSE/BCI-tests
4 participants
@grooverdan @dirkmueller @alexandrevicenzi @rcmadhankumar