[MDEV-19233] mysql_upgrade is not executed on package upgrade on Debian Created: 2019-04-10  Updated: 2019-04-28  Resolved: 2019-04-28

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian, Scripts & Clients
Affects Version/s: 10.1.37, 10.2.23
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jean Weisbuch Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Debian Stretch AMD64

Issue Links:
Duplicate
is duplicated by MDEV-12576 Upgrade MariaDB 10.0 from Distro to 1... Closed
is duplicated by MDEV-14622 Running mysql_upgrade in background u... Closed

 Description   

It seems that mysql_upgrade is not (always?) executed automatically anymore on packages upgrade on recent Debian using the MariaDB repositories.

For example, on two fresh Debian Stretch (using systemd), upgrading from MariaDB 10.1.37 (from the Debian repository) to a 10.2.23 (from the MariaDB repository) did need to manually execute mysql_upgrade after the packages upgrade ended and the servers were running for a few minutes (the debian-start script was not running anymore).

I recall having a similar issue on upgrade from 10.0 to 10.1 on Debian Jessie (both from the MariaDB repository).

 Comments   
Comment by Elena Stepanova [ 2019-04-28 ]

Yes, there is a notorious race condition around mysql_upgrade on deb-based systems, which unfortunately remains unresolved so far.
Here are a couple of open issues about it: MDEV-14622 MDEV-12576 , possibly there are even more.

Generated at Thu Feb 08 08:50:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.