Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.6.11
-
None
Description
If a user runs mariadb-upgrade --force on a Debian Sid instance with MariaDB 10.6 it will error with:
...
|
sys.x$user_summary OK
|
sys.x$user_summary_by_file_io OK
|
sys.x$user_summary_by_file_io_type OK
|
sys.x$user_summary_by_stages OK
|
sys.x$user_summary_by_statement_latency OK
|
sys.x$user_summary_by_statement_type OK
|
sys.x$wait_classes_global_by_avg_latency OK
|
sys.x$wait_classes_global_by_latency OK
|
sys.x$waits_by_host_by_latency OK
|
sys.x$waits_by_user_by_latency OK
|
sys.x$waits_global_by_latency OK
|
Phase 4/7: Running 'mysql_fix_privilege_tables'
|
ERROR 12609 (HY000) at line 777: System table spider_tables is different version
|
ERROR 12609 (HY000) at line 778: System table spider_tables is different version
|
ERROR 12609 (HY000) at line 796: System table spider_tables is different version
|
ERROR 1007 (HY000) at line 801: Can't create database 'performance_schema'; database exists
|
FATAL ERROR: Upgrade failed
|
This is reproducible in CI, see job that upgraded MariaDB 10.5 in Debian Buster to 10.6 and Debian Sid: https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/3733845
Also 10.3 in Buster to 10.6 upgrade: https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/3733850