[MDEV-29486] mariadb-upgrade does not upgrade Created: 2022-09-07  Updated: 2023-02-17

Status: Open
Project: MariaDB Server
Component/s: Upgrades
Affects Version/s: 10.5, 10.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Oli Sennhauser Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: beginner-friendly
Environment:

Linux, n.a.


Issue Links:
Relates
relates to MDEV-29487 mariadb-upgrade does not detect upgra... Open
relates to MDEV-29487 mariadb-upgrade does not detect upgra... Open

 Description   

The Utility mariadb_upgrade does NOT upgrade but prints message:

mariadb-upgrade --user=root
This installation of MariaDB is already upgraded to 10.6.7-MariaDB.
There is no need to run mysql_upgrade again for 10.6.9-MariaDB.
You can use --force if you still want to run mysql_upgrade

This by itself is not a real problem and can be solved by --force. But we have cases were it is NOT true!!!

10.4.13 still works OK 10.5.17 ff does NOT so it must be introduced in 10.5

See also next bug.



 Comments   
Comment by Robin Newhouse [ 2023-02-17 ]

Thanks for opening this ticket Oli. I will start taking a look at this.

But we have cases were it is NOT true!!!

Do you mean cases where --force does not run mysql_upgrade successfully? Can you specify where this would be not true?

Comment by Oli Sennhauser [ 2023-02-17 ]

I meant: The message "there is no need to run mysql_upgade again" is NOT true. We had some cases where a forced mysql_upgrade was taking nearly an hour (zillions of tables)!

So in my opinion it should behave something like this:

if server_version == dd_version
do nothing and exit
if server_version != dd_version
check if there is something to upgrade
if there is something to upgrade
do upgrade and change the mysql_upgrade_info file
else
silently change the mysql_upgrade_info file
print message upgrade done.

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