2016-05-03 10:15:16 |
Robie Basak |
bug |
|
|
added bug |
2016-05-11 06:55:47 |
Lars Tangvald |
mysql-5.7 (Ubuntu): status |
Triaged |
In Progress |
|
2016-05-13 08:54:02 |
Lars Tangvald |
attachment added |
|
0001-Change-d-additions-debian-start-to-no-op.patch https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1577712/+attachment/4661903/+files/0001-Change-d-additions-debian-start-to-no-op.patch |
|
2016-05-13 12:33:40 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
2016-05-13 12:33:46 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
2016-06-21 11:02:18 |
Launchpad Janitor |
mysql-5.7 (Ubuntu): status |
In Progress |
Fix Released |
|
2016-06-21 11:17:18 |
Robie Basak |
nominated for series |
|
Ubuntu Xenial |
|
2016-06-21 11:17:18 |
Robie Basak |
bug task added |
|
mysql-5.7 (Ubuntu Xenial) |
|
2016-06-21 11:17:25 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): status |
New |
Triaged |
|
2016-06-21 11:17:29 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): importance |
Undecided |
High |
|
2016-07-13 14:25:31 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): status |
Triaged |
In Progress |
|
2016-07-13 14:25:35 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): assignee |
|
Robie Basak (racb) |
|
2016-07-14 11:21:27 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): milestone |
|
xenial-updates |
|
2016-07-14 11:22:34 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): milestone |
xenial-updates |
ubuntu-16.04.1 |
|
2016-07-14 12:38:48 |
Lars Tangvald |
description |
Due to the old upstart script still being active, mysql_upgrade is called both via upstart on daemon start and by mysql-server-5.7.postinst when upgrading on a system that is running upstart. This seems to cause various mysql_upgrade failures.
Let's use this bug to track this particular root cause, since it isn't clear that all the other classes of report will be cleared up by this fix although we think that they may be. We can dupe them in as needed as we find out. |
Due to the old upstart script still being active, mysql_upgrade is called both via upstart on daemon start and by mysql-server-5.7.postinst when upgrading on a system that is running upstart. This seems to cause various mysql_upgrade failures. mysql_upgrade will alter the structure of the system tables, particularly performance_schema, which it will delete and recreate. If one process deletes it, then the other creates it, the first will also try to create it, throwing an error.
[Impact]
Error causes mysql_upgrade to fail, which in turn makes the package installation fail.
[Test case]
Difficult to test fully since it's a race condition bug with two upgrade processes running together.
* Install mysql-server in Ubuntu Trusty
* Upgrade system to Xenial
Expected behavior:
The server installs, and the database is upgraded to support 5.7
Actual behavior:
Occasionally fails with errors like 'performance_schema does not exist' or 'performance_schema already exists'.
[Regression potential]
Debian-start is made a no-op script, so if it did something useful we haven't noticed, that's lost.
---
Let's use this bug to track this particular root cause, since it isn't clear that all the other classes of report will be cleared up by this fix although we think that they may be. We can dupe them in as needed as we find out. |
|
2016-07-15 19:24:51 |
Adam Conrad |
mysql-5.7 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
2016-07-15 19:24:53 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2016-07-15 19:24:55 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
2016-07-15 19:24:59 |
Adam Conrad |
tags |
patch |
patch verification-needed |
|
2016-07-20 13:38:54 |
Robie Basak |
tags |
patch verification-needed |
patch 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 |
|