[Bug 1915734] Re: The db-sync command fails with MySQL 8

[Brian Murray]

Hello Ionut-Madalin, or anyone else affected,

Accepted magnum into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/magnum/11.0.0-0ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: magnum (Ubuntu Groovy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-groovy

-- 
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:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in magnum package in Ubuntu:
  Fix Released
Status in magnum source package in Focal:
  Fix Committed
Status in magnum source package in Groovy:
  Fix Committed

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