MySQL Bugs: #107224: missleading Redo log format is error

Bug #107224	missleading Redo log format is error
Submitted:	5 May 2022 17:01	Modified:	6 May 2022 6:21
Reporter:	Marcelo Altmann	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Logging	Severity:	S3 (Non-critical)
Version:	8.0.29	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This is a low hanging:

After the introduction of e8f422de8595f65f05f88ea4d4c94c7dfd365afd. there is a new redo log version (v5).
This makes error message ER_IB_MSG_704 be incorrect as it has version 8.0.3 hardcorded.

For example, upgrade MySQL from 8.0.28 to 8.0.29 you will get:

2022-05-05T16:56:20.812766Z 1 [Note] [MY-012529] [InnoDB] Redo log format is v4. The redo log was created before MySQL 8.0.3.

How to repeat:

start mysql 8.0.29 on a 8.0.28 datadir (use --log-error-verbosity=3)

Suggested fix:
either adjust ER_IB_MSG_704 to take a server version as parameter or create a new message to reflect log been created prior to 8.0.29

Hello Marcelo,

Thank you for the report and feedback.

regards,
Umesh

Wasn't this one fixed as of 8.0.30?
In my upgrade test, the log entry looks sane now, also the redo log is upgraded automatically, not like it was in 8.0.29:

2022-09-19T08:20:12.012822Z 1 [Note] [MY-012529] [InnoDB] Redo log format is v4. The redo log was created before MySQL 8.0.30.
2022-09-19T08:20:12.056008Z 1 [Note] [MY-012557] [InnoDB] Redo log is from an earlier version, v4.
2022-09-19T08:20:12.057534Z 1 [Note] [MY-012532] [InnoDB] Applying a batch of 0 redo log records ...
2022-09-19T08:20:12.057625Z 1 [Note] [MY-012535] [InnoDB] Apply batch completed!
2022-09-19T08:20:12.058561Z 1 [Note] [MY-013888] [InnoDB] Upgrading redo log: 0M, LSN=18229772.
2022-09-19T08:20:12.060926Z 1 [Note] [MY-012968] [InnoDB] Starting to delete and rewrite redo log files.
2022-09-19T08:20:12.221052Z 1 [Note] [MY-012893] [InnoDB] New redo log files created, LSN=18230284
2022-09-19T08:20:12.221140Z 1 [Note] [MY-013083] [InnoDB] Log background threads are being started...
...
2022-09-19T08:20:19.371998Z 4 [System] [MY-013381] [Server] Server upgrade from '80028' to '80030' completed.