Bug #90686 Authentication plugin 'caching_sha2_password' is not supported
Submitted: 30 Apr 2018 8:57 Modified: 12 Aug 2018 15:07
Reporter: Shiv Iyer Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Utilities Severity:S3 (Non-critical)
Version: OS:CentOS
Assigned to: CPU Architecture:Any

[30 Apr 2018 8:57] Shiv Iyer
Description:
mysqldiskusage: error: Authentication plugin 'caching_sha2_password' is not supported

Infrastructure details 

[root@localhost bin]# rpm -qa | grep mysql-utilities 
mysql-utilities-1.6.5-1.el7.noarch
[root@localhost bin]# 

[root@localhost bin]# rpm -qa | grep mysql-connector 
mysql-connector-python-2.1.7-1.el7.x86_64
[root@localhost bin]# 

mysql> select version();
+-----------+
| version() |
+-----------+
| 8.0.11    |
+-----------+
1 row in set (0.00 sec)

mysql> 

[root@localhost bin]# cat /etc/redhat-release 
CentOS Linux release 7.4.1708 (Core) 

How to repeat:
[root@localhost bin]# mysqldiskusage --server=root:India/2018@localhost employees --all 
WARNING: Using a password on the command line interface can be insecure.
# Source on localhost: ... 
Usage: mysqldiskusage --server=user:pass@host:port:socket db1 --all

mysqldiskusage: error: Authentication plugin 'caching_sha2_password' is not supported
[root@localhost bin]# 

Suggested fix:

I think MySQL utilities need to built MySQL 8. ready , considering so much advancements in MySQL 8
[30 Apr 2018 9:06] MySQL Verification Team
Thank you for the bug report. Duplicate of https://bugs.mysql.com/bug.php?id=90682
[12 Jul 2018 13:12] Chuck Bell
Not a duplicate. This is an original defect.
[12 Jul 2018 15:07] Chuck Bell
Please upgrade to Connector/Python 8.0.11 or later to fix this error.
[13 Jul 2018 7:22] MySQL Verification Team
Confirmed that after upgrading to mysql-connector-python-8.0.11, issue is not there but again it is affected by the installation issue Bug#88376 (Bug#90682) and have to use workaround in order to work.

#### installation details are at Bug#90682
root@BugCentOS7 Downloads]# mysql -uroot -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 22
Server version: 8.0.11 MySQL Community Server - GPL

Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> use db1
Database changed
mysql> create table t1(id int not null);
Query OK, 0 rows affected (0.10 sec)

mysql> \q
Bye
[root@BugCentOS7 Downloads]# mysqldiskusage --server='root':'Mysql123!'@localhost db1 --all
WARNING: Using a password on the command line interface can be insecure.
# Source on localhost: ... connected.
# Database totals:
+----------+----------+
| db_name  |   total  |
+----------+----------+
| db1      | 114,708  |
+----------+----------+

Total database disk usage = 114,708 bytes or 112.02 KB

# Log information.
# The general_log is turned off on the server.
# The slow_query_log is turned off on the server.
+-------------+---------+
| log_name    |   size  |
+-------------+---------+
| mysqld.log  | 25,073  |
+-------------+---------+

Total size of logs = 25,073 bytes or 24.49 KB

# Binary log information:
Current binary log file = binlog.000001
+----------------+-------+
| log_file       | size  |
+----------------+-------+
| binlog.000001  | 520   |
| binlog.index   | 16    |
+----------------+-------+

Total size of binary logs = 536 bytes

# Server is not an active slave - no relay log information.
# InnoDB tablespace information:
+--------------+-------------+
| innodb_file  |       size  |
+--------------+-------------+
| ib_logfile0  | 50,331,648  |
| ib_logfile1  | 50,331,648  |
| ibdata1      | 12,582,912  |
+--------------+-------------+

Total size of InnoDB files = 113,246,208 bytes or 108.00 MB

#...done.
[13 Aug 2018 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".