MySQL Bugs: #88159: log-slave-updates warning & replication setup messages on non-replication setup

Bug #88159	log-slave-updates warning & replication setup messages on non-replication setup
Submitted:	20 Oct 2017 1:12	Modified:	20 Oct 2017 6:34
Reporter:	Roel Van de Paar	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	8.0.3 RC	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Few questions (may or may not be bugs);

1) "You need to use --log-bin to make --log-slave-updates work." - this is shown at startup even if "--log-slave-updates work" is not being used (nor any other binlog option)? 
2) Replication setup messages (ref below) are shown even if no binlog options etc. are used?

How to repeat:
Startup Server with --no-defaults

2017-10-20T00:40:21.394303Z 0 [Note] Basedir set to /sda/PS161017-mysql-8.0.3-rc-linux-x86_64-debug/
2017-10-20T00:40:21.396751Z 0 [Warning] You need to use --log-bin to make --log-slave-updates work.
2017-10-20T00:40:34.673837Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 48c03c98-b52f-11e7-8195-902b34625689.
2017-10-20T00:40:34.682819Z 0 [Warning] You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.

Hello Roel,

Thank you for the report and feedback.

-- Reported warning observed when initializing with --initialize*(this stuff is not logged), but log_slave_update/log-slave-updates was turned on by default in 8.0.3.

bin/mysqld --no-defaults --initialize-insecure --basedir=$PWD --datadir=$PWD/88161
2017-10-20T06:00:04.003335Z 0 [Note] Basedir set to /export/umesh/server/binaries/Trunk/mysql-8.0.3/
2017-10-20T06:00:04.003532Z 0 [Warning] The syntax '--symbolic-links/-s' is deprecated and will be removed in a future release
2017-10-20T06:00:04.006489Z 0 [Warning] You need to use --log-bin to make --log-slave-updates work.
2017-10-20T06:00:04.884058Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: eb162ebd-b55b-11e7-8119-0010e05f3e06.
2017-10-20T06:00:04.884572Z 0 [Warning] You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.
2017-10-20T06:00:04.886442Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2017-10-20T06:00:05.545165Z 0 [Warning] CA certificate ca.pem is self signed.
2017-10-20T06:00:05.720692Z 5 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.

-- Startup messages - no such earlier warning observed since log_bin/log-slave-updates enabled by default

 bin/mysqld --no-defaults --sql_mode= --basedir=$PWD --datadir=$PWD/88161 --core-file --socket=/tmp/mysql_ushastry.sock --port=3306 --log-error=$PWD/88161/log.err 2>&1 &

 -- extract from error log -- this time no warning related to --log-bin and --log-slave-update since bin-log is enabled by default in 8.0.3
 
2017-10-20T06:16:49.696425Z 0 [Note] Basedir set to /export/umesh/server/binaries/Trunk/mysql-8.0.3/
2017-10-20T06:16:49.696744Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2017-10-20T06:16:49.696798Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-10-20T06:16:49.696838Z 0 [Note] /export/umesh/server/binaries/Trunk/mysql-8.0.3/bin/mysqld (mysqld 8.0.3-rc-enterprise-commercial-advanced-log) starting as process 26402 ...
2017-10-20T06:16:49.701866Z 0 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hod03-bin' to avoid this problem.

Thanks,
Umesh