Bug #101657 Unable to get innodb cluster status after upgrading from 8.0.18 to 8.0.22
Submitted: 18 Nov 2020 6:59 Modified: 19 Nov 2020 5:41
Reporter: k n Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.22 OS:Debian (Debian 10)
Assigned to: MySQL Verification Team CPU Architecture:x86

[18 Nov 2020 6:59] k n
Description:
After upgrading from mysql 8.0.18 to 8.0.22 I am unable to look up cluster status using mysql-shell. It was showing the status on 8.0.18 before the ugprade.

Trying to look up innodb cluster using mysql-shell, I connect to a cluster instance and try to display the cluster status but returns an error

"Dba.getCluster: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (utf8_general_ci,SYSCONST) for operation '=' (RuntimeError)"

From the logs I can see that this is the problematic query mysql-shell is trying to execute:

SELECT (SELECT COUNT(*) FROM `mysql_innodb_cluster_metadata`.instances WHERE cluster_id = (SELECT cluste
r_id FROM `mysql_innodb_cluster_metadata`.instances WHERE mysql_server_uuid=@@server_uuid)) = (SELECT count(*) FROM performance_schema.replication_group
_members WHERE member_state = 'ONLINE') as all_online

It looks like @@server_uuid is returning a different collation (ascii_general_ci,IMPLICIT) to mysql_innodb_cluster_metadata.mysql_server_uuid

How to repeat:
1. Using mysql-shell connect to a cluster instance

\connect user@server:6446

2. Try to get the cluster status

var cluster = dba.getCluster("ProdCluster");
cluster.status();

"Dba.getCluster: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (utf8_general_ci,SYSCONST) for operation '=' (RuntimeError)"
[18 Nov 2020 10:09] Frederic Descamps
Hello, 

Are you also using the latest MySQL Shell (8.0.22) ?

cheers,
[18 Nov 2020 11:52] MySQL Verification Team
Hi,

> After upgrading from mysql 8.0.18 to 8.0.22

As my colleague asked, did you upgrade the shell too?

all best
Bogdan
[19 Nov 2020 0:37] k n
It was my user error. Incorrect version of mysql-shell was used. Upgrading mysql-shell to the same version as the server resolved. This was a false positive bug report.
[19 Nov 2020 5:41] MySQL Verification Team
Thanks for the update

all best
Bogdan