[Bug 1915734] Re: The db-sync command fails with MySQL 8
Launchpad Bug Tracker
1915734 at bugs.launchpad.net
Mon Nov 1 19:41:19 UTC 2021
This bug was fixed in the package magnum - 10.0.0-0ubuntu0.20.04.2
---------------
magnum (10.0.0-0ubuntu0.20.04.2) focal; urgency=medium
* d/control: Update VCS paths for move to lp:~ubuntu-openstack-dev.
* d/p/mysql8-support.patch: Picked from upstream stable/ussuri review
https://review.opendev.org/c/openstack/magnum/+/781510 for mysql 8
support (LP: #1915734).
* d/rules: Add OS_STDOUT_CAPTURE/OS_STDERR_CAPTURE to test execution
inline with upstream.
-- Chris MacNaughton <chris.macnaughton at ubuntu.com> Mon, 26 Apr 2021
14:13:36 +0000
** Changed in: magnum (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1915734
Title:
The db-sync command fails with MySQL 8
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive ussuri series:
Fix Committed
Status in Ubuntu Cloud Archive victoria series:
Fix Committed
Status in magnum package in Ubuntu:
Fix Released
Status in magnum source package in Focal:
Fix Released
Status in magnum source package in Groovy:
Won't Fix
Bug description:
[Impact]
New installations of OpenStack Magnum with Mysql8 fail with a
traceback when trying to initialize the database
[Test Case]
Use the OpenStack charms to deploy Mggnum on Ubuntu Focal. Using Focal
is expected to have a traceback and with this change is expected to
setup successfully.
[Regression Potential]
The regression potential for this is minimal as the package currently
does not work at all with mysql8 which ships with Ubuntu Focal and
above. This change has already landed into the upstream project, both
on Master and in their stable branches.
The proposed change is a cherry-pick from upstream that resolves this
issue by updating the old migrations to not set constraints that break
on Mysql8. This only affects new deploys that would normally step
through all of the old migrations so shouldn't affect running deploys.
----------------------------------------------
The command to do the Magnum DB sync ('magnum-db-manage upgrade')
fails when using MySQL 8 releases.
This issue is tracked in the upstream Magnum project at:
https://storyboard.openstack.org/#!/story/2008488.
There is a fix already merged on Magnum master branch to fix this:
https://review.opendev.org/c/openstack/magnum/+/774142
We need to have this fix included with Magnum distro packages that are
expected to use MySQL 8. For example, deployments on Ubuntu Focal (or
higher) are expected to be using MySQL 8 already.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1915734/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list