Bug#299Bug#29995256: PRIVILEGE_CHECKS_USER NOT CLONED FOR RECOVERY CHANNEL

pedrolgomes · dahlerlend · commit abe87f83d947 · 2019-12-09T11:12:05.000+01:00
Bug#30510766: SLAVE FAILS TO START AFTER BEING CLONED IF USING POSITIONS

[Post fix]

To work on windows the rpl_cloned_slave_relay_log_info test needs to
prevent the members from starting their slave channels on restart. We
only guaranteed that on systems that need mysqld_safe.

ReviewBoard: 23489
diff --git a/mysql-test/suite/rpl/t/rpl_cloned_slave_relay_log_info-master.opt b/mysql-test/suite/rpl/t/rpl_cloned_slave_relay_log_info-master.opt
@@ -1 +1,2 @@
 $CLONE_PLUGIN_OPT
+--skip-slave-start=1
diff --git a/mysql-test/suite/rpl/t/rpl_cloned_slave_relay_log_info.test b/mysql-test/suite/rpl/t/rpl_cloned_slave_relay_log_info.test
@@ -249,8 +249,11 @@ UNINSTALL PLUGIN clone;
 
 --source include/clean_monitoring_process.inc
 
+# mysqld_safe restarts but does not start slave channels
+--disable_warnings
 --let $rpl_channel_name=
 --source include/stop_slave.inc
+--enable_warnings
 
 RESET SLAVE ALL;
 

Original file line number	Diff line number	Diff line change
`@@ -1 +1,2 @@`
`1`	`1`	`$CLONE_PLUGIN_OPT`
	`2`	`+--skip-slave-start=1`