This bug was fixed in the package mysql-5.7 - 5.7.13-0ubuntu0.16.04.2
---
mysql-5.7 (5.7.13-0ubuntu0.16.04.2) xenial-security; urgency=medium
* SECURITY UPDATE: Update to 5.7.13 to fix security issues (LP: #1604796)
-
Verified:
echo "invalid_mysql_option=foo" >> /etc/mysql/my.cnf.
Then on upgrade it should fail to start and complain - now with a reasonable
message.
Going from Trusty -> Xenial-Proposed now with aforementioned change in place I
see:
ERROR: Unable to start MySQL server:
Hello Robie, or anyone else affected,
Accepted mysql-5.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mysql-5.7/5.7.12-0ubuntu1.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Uploaded to Xenial. SRU team: you may find it easier to review if you
verify my uploaded delta is the same as
https://git.launchpad.net/~racb/ubuntu/+source/mysql-5.7/log/?h=mysql-5.7/ubuntu/xenial
and then use that.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[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
** Changed in: mysql-5.7 (Ubuntu Xenial)
Milestone: None => xenial-updates
** Changed in: mysql-5.7 (Ubuntu Xenial)
Milestone: xenial-updates => ubuntu-16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
