Comment 3 for bug 1901708

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thanks for taking the time to report this bug and make Ubuntu better.

Even though I am not able to reproduce the bug in a simple environment, this seems like a real problem indeed.

Basically, what you (or your system, rather) tried to do was to upgrade to the latest version of mysql-server (from 8.0.21-0ubuntu0.20.04.4 to 8.0.22-0ubuntu0.20.04.2). This requires a "server upgrade" operation to be done by mysql, which in turn can take several minutes to complete, as can be seen in your logs:

2020-10-27T13:55:29.166278Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' started.
2020-10-27T13:59:53.420927Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' completed.

In your case, the operation took almost 5 minutes to complete. A similar bug (LP 1901711) was reported, in which we can also verify this behaviour:

2020-10-27T14:28:40.467183Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' started.
2020-10-27T14:35:31.474308Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' completed.

Almost 7 minutes to complete the internal upgrade. As I said above, I could not reproduce the bug here (my server upgrade took about 30 seconds), but I think it's because I don't have a big MySQL database populated here.

My guess (without investigating much further) is that some timeout is being reached, which is preventing the apt upgrade process to finish. But based on the mysql error.log, it seems that everything succeeded and you might be able to run an "apt upgrade" again just to finish what was left.

I'm subscribing Ubuntu Server to the bug; we will investigate more when we have more time available. Thanks.