Bug #121493 MySQL Shell Upgrade Checker reports 3 errors but output identifies only 1 actual error during upgrade validation
Submitted: 13 Oct 7:22 Modified: 13 Oct 14:50
Reporter: Ashwini Patil Email Updates:
Status: Verified Impact on me:
None 
Category:Shell Upgrade Checker Severity:S3 (Non-critical)
Version:8.0.36 OS:Red Hat
Assigned to: CPU Architecture:x86
Tags: group replicaiton, mysql innodb cluster, mysql shell

[13 Oct 7:22] Ashwini Patil
Description:
We are preparing for an upgrade from MySQL Server 8.0.36 to MySQL Server 8.4.10 because MySQL 8.0 has reached End of Life.

As part of our pre-upgrade validation process, we are running the MySQL Shell Upgrade Checker utility.

mysqlsh -- util checkForServerUpgrade \
'user@host:3306' \
--target-version=8.4.10 \
--config-path=/etc/my.cnf

The Upgrade Checker summary indicates that there are 3 errors preventing the upgrade.

However, when reviewing the detailed report:

Only 1 item is reported as an Error
The remaining findings are categorized as Warnings and Notices
No additional Error entries corresponding to the reported error count are displayed.

Because the utility reports 3 errors in the summary but provides details for only 1 error, we are unable to determine what the other two blocking issues are and therefore cannot proceed with upgrade remediation.

Can Oracle provide guidance on how to identify the two undisclosed errors?

The issue is observed on all nodes of the InnoDB Cluster. The Upgrade Checker output is consistent across nodes, with the summary indicating 3 errors while the detailed report exposes only 1 error. This behavior appears to be independent of the individual node being checked.

How to repeat:
Install MySQL Server 8.0.36 on a RHEL server.
Install MySQL Shell 8.4.1.
Configure the server.
Run the MySQL Shell Upgrade Checker against the server:

mysqlsh -- util checkForServerUpgrade \
'user@host:3306' \
--target-version=8.4.10 \
--config-path=/etc/my.cnf

Review the Upgrade Checker summary output.
Observe that the summary reports 3 Errors.
Review the detailed findings section of the report.
Observe that only 1 finding is categorized as an Error, while all remaining findings are classified as Warnings or Notices.
No details are provided for the additional 2 errors included in the summary count.

Suggested fix:
Expected Behavior

The Upgrade Checker should:

Either display details for all reported errors
Or report the correct error count in the summary

Actual Behavior
Summary reports 3 errors
Detailed output contains only 1 error
Remaining findings are warnings/notices
No indication of the additional 2 errors

Impact

The upgrade activity is currently blocked because we cannot identify or remediate the hidden errors that the summary reports.
[13 Oct 14:50] Pawel Andruszkiewicz
Hi, the two missing errors are accounts reported under:

9) Check for deprecated or invalid authentication methods in use by MySQL
Router internal accounts. (deprecatedRouterAuthMethod)
   Warning: The following accounts are MySQL Router accounts that use a
   deprecated authentication method.

The "Warning" in this message is hard-coded, but the severity in this case is "error".

Also, please always use the latest MySQL Shell (currently 26.7.0).