MySQL Bugs: #90535: MySQL Shell unable to retrieve data from table with 0 month in TIMESTAMP column

Bug #90535	MySQL Shell unable to retrieve data from table with 0 month in TIMESTAMP column
Submitted:	20 Apr 2018 14:15	Modified:	20 Apr 2018 14:21
Reporter:	Ryusuke Kajiyama	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Document Store: MySQL Shell	Severity:	S3 (Non-critical)
Version:	8.0.11	OS:	MacOS (10.12.6)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Shell returns ERROR on SELECTing data from table with 0 month in TIMESTAMP column.
====
 MySQL  localhost:3310 ssl  SQL > SELECT * FROM performance_schema.replication_connection_status \G
ERROR: ClassicResult.fetchOne: Valid month range is 1-12
====

It is also potentially bug of InnoDB Cluster setup with MySQL Shell. Though sql_mode has NO_ZERO_IN_DATE,NO_ZERO_DATE, performance_schema.replication_connection_status contains 0000-00-00 00:00:00.000000 in TIMESTAMP columns

How to repeat:
set PATH of bin of MySQL Sever, Shell and Router

in MySQL Shell
====
 MySQL  JS > dba.deploySandboxInstance(3310)

 MySQL  JS > \connect root@localhost:3310

 MySQL  localhost:3310 ssl  JS > cluster = dba.createCluster("myCluster")

 MySQL  localhost:3310 ssl  JS > \sql
Switching to SQL mode... Commands end with ;

 MySQL  localhost:3310 ssl  SQL > SELECT * FROM performance_schema.replication_connection_status \G
ERROR: ClassicResult.fetchOne: Valid month range is 1-12
====

in mysql client;
====
mysql> SELECT * FROM performance_schema.replication_connection_status \G
*************************** 1. row ***************************
                                      CHANNEL_NAME: group_replication_applier
                                        GROUP_NAME: 586c0230-44a3-11e8-8cba-f65add46c817
                                       SOURCE_UUID: 586c0230-44a3-11e8-8cba-f65add46c817
                                         THREAD_ID: NULL
                                     SERVICE_STATE: ON
                         COUNT_RECEIVED_HEARTBEATS: 0
                          LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00.000000
                          RECEIVED_TRANSACTION_SET: 46f2944c-44a3-11e8-b8a6-b663cdd8d295:1-14,
586c0230-44a3-11e8-8cba-f65add46c817:1-2
                                 LAST_ERROR_NUMBER: 0
                                LAST_ERROR_MESSAGE: 
                              LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
                           LAST_QUEUED_TRANSACTION: 586c0230-44a3-11e8-8cba-f65add46c817:1
 LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
     LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 2018-04-20 23:01:42.334502
       LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 2018-04-20 23:01:42.334563
                              QUEUEING_TRANSACTION: 
    QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
   QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
        QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
1 row in set (0.00 sec)

mysql> SHOW VARIABLES LIKE 'sql_mode';
+---------------+-----------------------------------------------------------------------------------------------------------------------+
| Variable_name | Value                                                                                                                 |
+---------------+-----------------------------------------------------------------------------------------------------------------------+
| sql_mode      | ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION |
+---------------+-----------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
====

Duplicate with #90355