Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1(EOL), 10.2(EOL), 10.3(EOL)
-
None
Description
Our upgrade tests run mysql_upgrade -uroot without sudo (which shouldn't be necessary, since authentication doesn't use unix_socket plugin). It does the job all right, but at the end it complains about not being able to create /var/lib/mysql/mysql_upgrade_info. It doesn't make it fail, though.
I didn't try to reproduce it manually, but I expect it should be the same.
Maybe it's just a documentation issue and it's supposed to be always run under sudo.
No information about 10.0.
Attachments
Issue Links
- relates to
-
MDEV-23008 store mysql_upgrade version info in system table instead of local file
-
- Open
-
-
MDEV-32166 mysql_install_db creates mysql_upgrade_info file with different owner
-
- Closed
-
- links to
Maybe the info should be in a mysql.schema_version table with a single row and column. This is the way application schema versions tend to be managed, at least alembic (python) when I used that. This would survive database sql backups and not require root/mysql user privs to mysql_upgrade_info.