| Bug #87105 | 8.0.1 --> 8.0.2 upgrade fails | ||
|---|---|---|---|
| Submitted: | 18 Jul 2017 18:24 | Modified: | 19 Jul 2017 15:31 |
| Reporter: | Peter Brawley (Basic Quality Contributor) | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S1 (Critical) |
| Version: | 8.0.2 | OS: | Ubuntu (16.04) |
| Assigned to: | CPU Architecture: | Any | |
[18 Jul 2017 19:28]
Peter Laursen
I had a similar problem on Win10 (using "Windows Installer"). I think it installed but the service did not start as expected and would not either on "net start ..". I uninstalled .01 and installed .02 (also from "Windows Installer") and everything now seems OK. I had no important data on 8.01, so no big deal for me. I think that there is no guarantee that upgrades between early non-GA versions is possible. What the reason is in this particular case, I don't know, but I don't care much either. We are on "experimental grounds" here. S... is supposed to happen. -- Peter -- not a MySQL/Oracle person
[18 Jul 2017 19:28]
Peter Laursen
I had a similar problem on Win10 (using "Windows Installer"). I think it installed but the service did not start as expected and would not either on "net start ..". I uninstalled .01 and installed .02 (also from "Windows Installer") and everything now seems OK. I had no important data on 8.01, so no big deal for me. I think that there is no guarantee that upgrades between early non-GA versions is possible. What the reason is in this particular case, I don't know, but I don't care much either. We are on "experimental grounds" here. S... is supposed to happen. -- Peter -- not a MySQL/Oracle person
[18 Jul 2017 19:35]
Peter Brawley
> We are on "experimental grounds" here. S... is supposed to happen. Might indeed, and did, but is not "supposed to".
[19 Jul 2017 6:32]
Lars Tangvald
Hi, As noted, upgrading from one dmr to another is not supported, since breaking changes can and will be introduced between them. There are incompatible changes in 8.0.2, but I'm not 100% sure if they would cause upgrade failures for simple databases. Can you check your server error log at /var/log/mysql/error.log?
[19 Jul 2017 10:47]
MySQL Verification Team
Thank you for the report. Verifying this as a doc request after discussing internally with Lars. regards, Umesh
[19 Jul 2017 14:31]
Paul DuBois
Posted by developer: DMR (development milestone releases) are by their nature "use at your own risk" and upgrades between them are not supported. https://dev.mysql.com/doc/refman/8.0/en/upgrading.html Upgrades between milestone releases (or from a milestone release to a GA release) are not supported. For example, upgrading from 8.0.0 to 8.0.1 is not supported, as neither are GA status releases.
[19 Jul 2017 15:31]
Peter Brawley
https://dev.mysql.com/doc/refman/8.0/en/upgrading.html says ... The process described here requires that you upgrade to MySQL 8.0 from a MySQL 5.7 GA version (5.7.9 or higher). Upgrades from non-GA versions of MySQL 5.7 or from MySQL series preceding 5.7 are not supported. It does not say that upgrade from 8.0.x to 8.0.x+1 is not supported. If that's so, that page needs to say so. And if possible, 8.0 releases should not be available as upgrades to previous 8.0 versions from the repository.
Description: Attempot to upgrade from 8.0.1 to 8.0.2 on Ubuntu 16.04 using ... sudo apt-get upgrade sudo apt-get install mysql-server failed ... Installing new version of config file /etc/init.d/mysql ... Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing package mysql-community-server (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-community-server (= 8.0.2-dmr-1ubuntu16.04); however: Package mysql-community-server is not configured yet. dpkg: error processing package mysql-server (--configure): dependency problems - leaving unconfigured Processing triggers for systemd (229-4ubuntu16) ... No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for ureadahead (0.100.0-19) ... Errors were encountered while processing: mysql-community-server mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1) The server installation has failed ... dpkg -l | grep mysql ii mysql-apt-config 0.8.4-1 all Auto configuration for MySQL APT Repo. ii mysql-client 8.0.2-dmr-1ubuntu16.04 i386 MySQL Client meta package depending on latest version ii mysql-common 8.0.2-dmr-1ubuntu16.04 i386 MySQL Common ii mysql-community-client 8.0.2-dmr-1ubuntu16.04 i386 MySQL Client ii mysql-community-client-core 8.0.2-dmr-1ubuntu16.04 i386 MySQL Client Core Binaries iF mysql-community-server 8.0.2-dmr-1ubuntu16.04 i386 MySQL Server ii mysql-community-server-core 8.0.2-dmr-1ubuntu16.04 i386 MySQL Server Core Binaires iU mysql-server 8.0.2-dmr-1ubuntu16.04 i386 MySQL Server meta package depending on latest version (Note also the repo report typo in the 2nd last line.) How to repeat: As above