Activity log for bug #1612517

Date Who What changed Old value New value Message
2016-08-12 06:39:59 Lars Tangvald bug added bug
2016-08-12 06:40:39 Lars Tangvald mysql-5.7 (Ubuntu): assignee Lars Tangvald (lars-tangvald)
2016-08-12 06:41:12 Launchpad Janitor mysql-5.7 (Ubuntu): status New Confirmed
2016-09-22 11:42:56 Robie Basak summary Server fails to start because of customized config Server fails to start after because of customized config and obsolete/renamed directives
2016-09-22 11:43:00 Robie Basak tags triage
2016-09-22 11:54:18 Robie Basak summary Server fails to start after because of customized config and obsolete/renamed directives Server fails to start after upgrade because of customized config and obsolete/renamed directives
2017-01-06 12:21:30 Robie Basak mysql-5.7 (Ubuntu): importance Undecided Medium
2019-11-13 13:51:53 Andreas Hasenack description 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. 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. By "custom config", we actually mean two possibilities: a) non-default config file (like /etc/mysql/my.cnf) b) non-default config option (like NO_AUTO_CREATE_USER, which was dropped in 8) 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.
2019-11-13 13:52:48 Andreas Hasenack description 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. By "custom config", we actually mean two possibilities: a) non-default config file (like /etc/mysql/my.cnf) b) non-default config option (like NO_AUTO_CREATE_USER, which was dropped in 8) 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. 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. The same can happen with any other upgrade, like from 5.7 to 8.0. By "custom config", we actually mean two possibilities: a) non-default config file (like /etc/mysql/my.cnf) b) non-default config option (like NO_AUTO_CREATE_USER, which was dropped in 8, but was never part of the default config files shipped with the package) 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.
2019-11-13 13:56:03 Andreas Hasenack bug task added mysql-8.0 (Ubuntu)
2019-11-13 13:56:22 Andreas Hasenack mysql-8.0 (Ubuntu): status New Confirmed
2019-11-13 13:56:28 Andreas Hasenack mysql-8.0 (Ubuntu): importance Undecided Medium
2020-12-08 10:32:43 Yriu Sicora removed subscriber Yriu Sicora
2021-03-23 00:00:29 Bryce Harrington marked as duplicate 1920188
2021-03-23 00:00:48 Bryce Harrington removed duplicate marker 1920188