** Description changed:
Separate from LP: #1571865 because this concerns options we don't try to
automatically fix.
When users upgrade from 5.5 (and especially if that was also an upgrade
from earlier versions) and have custom configs, 5.7 may refuse to start
because the config contai
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
** This bug is no longer a duplicate of bug 1850998
NO_AUTO_CREATE_USER removed in mysql-8, broke upgrade
** This bug has been marked a duplicate of bug 1612517
Server fails to start after upgrade beca
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
** This bug has been marked a duplicate of bug 1612517
Server fails to start after upgrade because of customized config and
obsolete/renamed directives
--
You received this bug notification because you
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
** This bug has been marked a duplicate of bug 1612517
Server fails to start after upgrade because of customized config and
obsolete/renamed directives
--
You received this bug notification because you
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
** This bug is no longer a duplicate of bug 1850895
query_cache_limit removed in mysql-8, upgrade broke
** This bug has been marked a duplicate of bug 1612517
Server fails to start after upgrade becaus
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
** This bug is no longer a duplicate of bug 1850998
NO_AUTO_CREATE_USER removed in mysql-8, broke upgrade
** This bug has been marked a duplicate of bug 1612517
Server fails to start after upgrade beca
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
The config option NO_AUTO_CREATE_USER is not part of the default config,
and therefore won't be taken care of during the upgrade to mysql 8. You
should remove it manually and then retry the installation with
A server-side mitigation was put in place and apt-get update shouldn't
fail anymore with esm disabled, but the sources.list snipped file in
place, on non-x86 arches. There is another issue still in that the ua
server is reporting esm-infra as being available for non-x86 arches,
which is incorrect.