Bug #81871 Upgrading mysql-server from apt repositories leaves server in BROKEN STATE
Submitted: 15 Jun 2016 21:43 Modified: 16 Jul 2016 11:42
Reporter: Karma Kolabor Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.6.31 OS:Ubuntu (14.04)
Assigned to: CPU Architecture:Any
Tags: amateur, broken change management, disaster, UPGRADE-FAIL

[15 Jun 2016 21:43] Karma Kolabor
Description:
I had a working installation of mysql with he default mysql server that comes with Ubuntu 14.04 LTS. I then installed mysql community server apt repository deb package and after apt-get update && apt-get upgrade the new server version 5.6.31 was installed. After this upgrade the SERVER DOES NOT START. 

This is absolutely unprofessional and annoying. I am not cross-upgrading from any other database with automatic imports of scripts or whatever, it is just a very simple upgrade of mysql from one version to another one - and this update breaks!

This is NOT acceptable. 

How to repeat:
Upgrade a standard Ubuntu 14.04 LTS to the one provided via apt repositories.

Suggested fix:
As these kind of primitive problems persist since more than a decade now with mysql and repeat over and over again I believe there is no fix for it.
[16 Jun 2016 10:17] Lars Tangvald
Hi,

Could you provide us with some more information to try to find the issue, here?

Did you only use apt-get upgrade/apt-get dist-upgrade after adding the the repo package? The mysql packages in Ubuntu 14 are named differently from the ones on repo.mysql.com (mysql-server-5.5/5.6 vs mysql-community-server), so apt-get upgrade will generally not complete the upgrade since doing so would require removing the Ubuntu packages.

Using apt-get dist-upgrade might upgrade the package, but apt might also decide not to do so if too many other packages would need to be changed.

As mentioned on http://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/ upgrading to the packages on repo.mysql.com should be done using apt-get install mysql-server.

Do you have the console output from the upgrade process available, or the MySQL error log?
[17 Jul 2016 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".