Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade cannot be repaired due to mysql-5.7 being unavailable after upgrade to Ubuntu 19.10

[Jeroen Van den Keybus]

Title says it all.

Although mysql_upgrade was run successfully on the original 5.7 database files, the in-place upgrade ran into trouble (invalid key field), causing mysql-8.0 to be unable to complete the table upgrade and generate the DD tables.

There is no way to repair this, as mysql-5.7, which is the only package that can operate on the database, is unavailable after the upgrade to Ubuntu 19.10.

The request is to keep mysql-5.7 available in Ubuntu 19.10, at least to be able to fix upgrade errors.

Thanks.

[Rafael David Tinoco (rafaeldtinoco)]

Hello Jeroen,

Can you provide steps so I can reproduce this issue ?

What parts of mysql_upgrade inplace upgrade are not working ?

Trying to reproduce I get:

$ sudo mysql_upgrade -u root -p
Enter password:
The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server.
To upgrade, please start the new MySQL binary with the older data directory. Repairing user tables is done automatically. Restart is not required after upgrade.
The upgrade process automatically starts on running a new MySQL binary with an older data directory. To avoid accidental upgrades, please use the --upgrade=NONE option with the MySQL binary. The option --upgrade=FORCE is also provided to run the server upgrade sequence on demand.
It may be possible that the server upgrade fails due to a number of reasons. In that case, the upgrade sequence will run again during the next MySQL server start. If the server upgrade fails repeatedly, the server can be started with the --upgrade=MINIMAL option to start the server without executing the upgrade sequence, thus allowing users to manually rectify the problem.

Have you tried --upgrade=MINIMAL option when restarting the deamon ?

I'm flaging this as incomplete until you provide more information AND a way we can reproduce what you have faced, but, there are some scenarios that mysqld might need manual intervention in the inplace update for it to finish.

Thank you

Rafael

[Rafael David Tinoco (rafaeldtinoco)]

Feel free to move this bug back to "New" when you report the requested information.

[Launchpad Janitor (janitor)]

[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.]