MySQL Bugs: #108311: MySQL Update to 8.0.30

Bug #108311	MySQL Update to 8.0.30
Submitted:	29 Aug 2022 1:42	Modified:	30 Aug 2022 12:24
Reporter:	Luke Coolhand	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	8.0.30	OS:	Fedora (F36)
Assigned to:		CPU Architecture:	x86 (Gen 12)

Description:
I have been running a database system for a few year using MySQL on Fedora. I kept up with regular updates, with both operating system and the MySQL server. It has been running smoothly for years. But, the latest update to MySQL 8.0.30 broke the system: After the update, the mysql service failed to start. The error log for the mysqld contains numerous lines such as:

---------

2022-08-27T07:20:09.972994Z 4 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=852] log sequence number 42688698848 is in the future! Current system log sequence number 42682823836.
2022-08-27T07:20:09.905480Z 4 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
...
2022-08-27T07:20:10.009722Z 0 [ERROR] [MY-013380] [Server] Failed to upgrade server.
2022-08-27T07:20:10.009741Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-08-27T07:20:11.394571Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld:   Shutdown complete (mysqld 8.0.30) Source distribution.

------

Maybe the new version is incompatible with the mysql.ibd file of older (presumably 8.0.29) version. First  time lunching the mysqld service, it attempts to covert the mysql.ibd file to the new version but failed.

I tried to remove all the databases and start the server with clean slate. It can start.

How to repeat:
No sure.

My system has been in running for a while. I converted the mysql.dbi to mysql.sdi, and try to import the sdi file, it says dd_version incompatible. The dd-version for the sdi file produced from the original mysql.idb file has version 80012.

Hi Mr. Coolhand,

Thank you for your bug report.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

We need a fully repeatable test case. This is due to the simple fact that millions of users have upgraded to 8.0.30 from 8.0.29, without any problems.  Hence, we need a fully repeatable test case.

Next, we strongly advise you to use our binaries from dev.mysql.com when installing any version / release of our product.

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.  

Thank you for your interest in MySQL.

I can repeat the process my self:

Remove files in /var/lib/mysql; start mysqld service. It will successfully start, and create all necessary files without any custom database. Can log in as root without password (cause the use table in mysql database is empty). Stop service; copy back the old mysql.ibd file as well as ibdata1/ib_log files from backup. Restart the mysqld server. The process of trying to update the mysql.ibd file will repeat again and the update would file again.

But whether this would repeat for other installations maybe questionable.  I have another database system running on another machine (F36+MySQL, but much older, 2009 era, machine, much smaller database). That system seems to upgrade to 8.0.30 without issue.

Sorry Mr. Coolhand,

But your method of upgrade is wrong. Please follow precisely instructions from our Reference Manual.