Server fails to start after upgrade because of customized config and obsolete/renamed directives
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Confirmed
|
Medium
|
Lars Tangvald | ||
mysql-8.0 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug 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. 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_
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://
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.
Changed in mysql-5.7 (Ubuntu): | |
assignee: | nobody → Lars Tangvald (lars-tangvald) |
summary: |
- Server fails to start because of customized config + Server fails to start after because of customized config and + obsolete/renamed directives |
tags: | added: triage |
summary: |
- Server fails to start after because of customized config and + Server fails to start after upgrade because of customized config and obsolete/renamed directives |
Changed in mysql-5.7 (Ubuntu): | |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
Changed in mysql-8.0 (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Status changed to 'Confirmed' because the bug affects multiple users.