Public bug reported: 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 contains options that have been removed. Options may have been removed due to becoming obsolete, or due to being renamed. Postinst will print the offending option to the terminal, but this might not be apparent in the text dump from a large upgrade operation. http://dev.mysql.com/doc/refman/5.7/en/mysqld-option-tables.html has a list of options that will be accepted for 5.7 The advantage of the current solution (print option name and throw error) is that after fixing the config, apt-get -f install should complete the upgrade fully. The disadvantage is that it will abort the upgrade process, which might be a full distro upgrade. The alternative would be to print a warning, which might not be noticed, and complete the install without running mysql_upgrade or starting the service. ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Assignee: Lars Tangvald (lars-tangvald) Status: Confirmed ** Changed in: mysql-5.7 (Ubuntu) Assignee: (unassigned) => Lars Tangvald (lars-tangvald) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612517 Title: Server fails to start because of customized config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
