6 Changes in MySQL Shell 8.0.38 (2024-07-01, General Availability)

MySQL Shell closed unexpectedly when calling certain AdminAPI functions on EL7 platforms. (Bug #36651010)
dba.reboot_cluster_from_complete_outage() disabled super_read_only on the primary member of an INVALIDATED Cluster. As a result, clients continued to perform updates and introduce errant transactions.
As of this release, dba.reboot_cluster_from_complete_outage() enables super_read_only on the primary member and disables the Group Replication action mysql_disable_super_read_only_if_primary. (Bug #36562916)
If an attempt to create a Replica Cluster failed due to a timeout and the revert also failed due to a timeout, the Replica Cluster could be left in an inconsistent state; ONLINE, but not associated with the ClusterSet's metadata. This specific issue was caused by low values for wait_timeout and interactive_timeout.
The following changes were made:
- wait_timeout is checked and, if set to a value lower than the default of 8 hours, is set to 8 hours.
- Cluster.rescan() is extended with a new option, repairMetadata which can be enabled to resolve inconsistencies in the Cluster's metadata.
- Cluster.dissolve() can now be used on Clusters in this inconsistent state.
(Bug #36495756)

Primary keys defined on an ENUM column were reported as missing for dumps with ocimds:true. This was caused by a fix in an earlier version which instructed the dump utility to ignore primary keys or unique indexes which contain one or more ENUM columns when selecting an index for chunking.
As of this release, information about the index selected for chunking and whether the table has a primary key is separated. (Bug #36493316)
References: See also: Bug #35180061.

MySQL Shell did not prompt for a password if -p was specified on the command line without an argument. (Bug #36433418)
Upgrading MySQL Shell 8.0.35, or higher, on Windows platforms, resulted in multiple installations instead of overwriting the existing installation. (Bug #113732, Bug #36259270)