MySQL Bugs: #96489: MySQL Shell configureInstance does not set binlog

Bug #96489	MySQL Shell configureInstance does not set binlog_checksum = NONE
Submitted:	9 Aug 2019 15:01	Modified:	25 Sep 2019 7:48
Reporter:	Truphone DBA	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Shell AdminAPI InnoDB Cluster / ReplicaSet	Severity:	S2 (Serious)
Version:	8.0.17	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Hi,
using MysQL Shell 8.0.17 
using:
dba.configureInstance() the option binlog_checksum=NONE is not set.

How to repeat:
MySQL Shell 8.0.17
MySQL Server 5.7.21

using: dba.configureInstance()

we see in my.cnf added:
---------------------
enforce_gtid_consistency = ON
gtid_mode = ON
log_slave_updates = ON
master_info_repository = TABLE
relay_log_info_repository = TABLE
transaction_write_set_extraction = XXHASH64
---------------------

And no:

binlog_checksum=NONE

Suggested fix:
Also add:
binlog_checksum=NONE

This is troublesome it you have your cluster being deployed using ansible/automation scripts.

As it makes the script unusable with this version of shell

Hello Pedro Pinheiro,

Thank you for the report and feedback.

regards,
Umesh

Posted by developer:
 
Thank you for your feedback, this has been fixed in upcoming versions and the following was added to the 8.0.18 changelog:

The dba.configureInstance() operation was not setting the binlog_checksum option with the required value (NONE) in the option file for instances that did not support SET PERSIST (for example instances running MySQL 5.7), when the option file path was not provided as an input parameter but instead specified though the operation wizard in interactive mode.