| 2016-07-13 16:33:31 |
Robie Basak |
bug |
|
|
added bug |
| 2016-07-13 16:33:40 |
Robie Basak |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-07-13 16:33:40 |
Robie Basak |
bug task added |
|
mysql-5.7 (Ubuntu Xenial) |
|
| 2016-07-13 16:33:46 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-07-13 16:33:49 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): assignee |
|
Robie Basak (racb) |
|
| 2016-07-13 16:34:00 |
Robie Basak |
description |
[Impact]
A common cause of upgrade failures are invalid configuration directives due to deprecation. In this kind of case, apport does not currently tell us the failure reason, and even if it did print a service start failure, the actual reason has to be dug out of the logs. Further, some users have a very old conffile that did not log output to the current location, so the real reason isn't always submitted in a bug report.
We can ask if mysqld will start by using: "mysqld --verbose --help --innodb-read-only 2>&1 > /dev/null". The postinst should do this so that it can fail early with a more useful error message.
This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352) but should also be SRU'd to Xenial.
Also see bug 1596056 and 1571865. Fixing each of these will improve the situation in a different way. Fixing all three bugs would catch the most failure cases and be the most helpful. |
[Impact]
A common cause of upgrade failures are invalid configuration directives due to deprecation. In this kind of case, apport does not currently tell us the failure reason, and even if it did print a service start failure, the actual reason has to be dug out of the logs. Further, some users have a very old conffile that did not log output to the current location, so the real reason isn't always submitted in a bug report.
We can ask if mysqld will start by using: "mysqld --verbose --help --innodb-read-only 2>&1 > /dev/null". The postinst should do this so that it can fail early with a more useful error message.
This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352) but should also be SRU'd to Xenial.
Also see bug 1596056 and bug 1571865. Fixing each of these will improve the situation in a different way. Fixing all three bugs would catch the most failure cases and be the most helpful. |
|
| 2016-07-14 11:21:37 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): milestone |
|
xenial-updates |
|
| 2016-07-14 11:22:16 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): milestone |
xenial-updates |
ubuntu-16.04.1 |
|
| 2016-07-14 12:54:41 |
Lars Tangvald |
description |
[Impact]
A common cause of upgrade failures are invalid configuration directives due to deprecation. In this kind of case, apport does not currently tell us the failure reason, and even if it did print a service start failure, the actual reason has to be dug out of the logs. Further, some users have a very old conffile that did not log output to the current location, so the real reason isn't always submitted in a bug report.
We can ask if mysqld will start by using: "mysqld --verbose --help --innodb-read-only 2>&1 > /dev/null". The postinst should do this so that it can fail early with a more useful error message.
This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352) but should also be SRU'd to Xenial.
Also see bug 1596056 and bug 1571865. Fixing each of these will improve the situation in a different way. Fixing all three bugs would catch the most failure cases and be the most helpful. |
[Impact]
A common cause of upgrade failures are invalid configuration directives due to deprecation. In this kind of case, apport does not currently tell us the failure reason, and even if it did print a service start failure, the actual reason has to be dug out of the logs. Further, some users have a very old conffile that did not log output to the current location, so the real reason isn't always submitted in a bug report.
We can ask if mysqld will start by using: "mysqld --verbose --help --innodb-read-only 2>&1 > /dev/null". The postinst should do this so that it can fail early with a more useful error message.
This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352) but should also be SRU'd to Xenial.
Also see bug 1596056 and bug 1571865. Fixing each of these will improve the situation in a different way. Fixing all three bugs would catch the most failure cases and be the most helpful.
mysqld --verbose --help doesn't currently catch all such issues (it returns 0 if datadir doesn't exist, for instance), but should be a help
[Test Case]
* Install previous version of MySQL (e.g. 5.5. in Trusty)
* Add something like 'invalid_mysql_option=foo' to the server config file
* Upgrade to Xenial and MySQL 5.7
Expected behavior:
A helpful error pointing to invalid_mysql_option
Actual behavior:
'subprocess installed post-installation script returned error exit status 1'
[Regression Potential]
Should there be any non-fatal issue that actually causes mysqld --verbose --help to fail but not the normal server startup to fail, the check will incorrectly cause installation to fail. |
|
| 2016-07-15 19:25:05 |
Adam Conrad |
mysql-5.7 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-07-15 19:25:07 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-07-15 19:25:09 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2016-07-15 19:25:13 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2016-07-20 13:22:25 |
Christian Ehrhardt |
tags |
verification-needed |
verification-done |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
mysql-5.7 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3424 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3459 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3477 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3486 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3501 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3518 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3521 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3588 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3614 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3615 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5436 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5437 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5439 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5440 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5441 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5442 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5443 |
|
