Comment 8 for bug 1725222
Revision history for this message
| Marco Marsala (marcomarsala) wrote Re: [Bug 1725222] Re: do-release-upgrade from Ubuntu 14.04 to 16.04.1 performs unsupported upgrade from MySQL 5.5 to 5.7 | #8 |
Yes I still experience the issue.
The problem described in #1577712 is not the only problem I experienced. Upgrading from 14.04 to 16.04.1 with do-release-upgrade break MySQL, we reproduced the same issue every time on many clean 14.04 installations. do-release-upgrade hangs on the post installation script for MySQL.
It seems the issue is upgrading directly from 5.5 to 5.7 is not supported, doing that (even manually) will hang on mysql_upgrade in many cases. Official MySQL documentation says: “Upgrade that skips versions is not supported. For example, upgrading directly from MySQL 5.5 to 5.7 is not supported.” - https:/
It may *seems* to work if you have only empty databases, but when we used it on production databases, with many data, it hung when it encountered features removed in 5.7, and you will have corrupted data (for example DATETIME fields with 0 default value, or the default SYS schema is missing version information).
MM
_______
From: Gunnar Hjalmarsson <<email address hidden>
Sent: martedì, ottobre 24, 2017 1:51 PM
Subject: [Bug 1725222] Re: do-release-upgrade from Ubuntu 14.04 to 16.04.1 performs unsupported upgrade from MySQL 5.5 to 5.7
To: <<email address hidden>
I see that bug #1577712 is marked "Fix Released". @Marco, did you
actually encounter problems when upgrading from 14.04 to 16.04? If so,
can you please elaborate on the nature of the problems?
--
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
do-release-upgrade from Ubuntu 14.04 to 16.04.1 performs unsupported
upgrade from MySQL 5.5 to 5.7
Status in Ubuntu Server Guide:
Invalid
Status in mysql-5.7 package in Ubuntu:
New
Status in ubuntu-
New
Bug description:
Updating from Ubuntu 14.04 to Ubuntu 16.04.1 using do-release-upgrade
will cause troubles because MySQL is upgraded from 5.5 to 5.7, that is
an unsupported update path, as per MySQL official documentation.
Your script should do these pre-checks and prevent upgrade, or
automatically solve the issue before applying upgrade.
PS: the solution is to upgrade MySQL in two steps, first from 5.5 to
5.6 then from 5.6 to 5.7.
To manage notifications about this bug go to:
https:/