mirror of
https://github.com/MariaDB/server.git
synced 2025-05-08 15:01:49 +03:00
4b157e1556
When passing an empty user to the connect function will cause valgrind warnings. Seems that the client code is not prepared to handle empty users. On 5.6 this can even be triggered by START SLAVE PASSWORD='...'; i.e., without setting USER='...' on the START SLAVE command (see WL#4143 for details on the new additional START SLAVE commands). To fix this, we disallow empty users when configuring the slave connection parameters (this decision might be revisited if the client code accepts empty users in the future). sql/slave.cc: We throw an error if an empty user is supplied to the connection function.
25 lines
696 B
Plaintext
25 lines
696 B
Plaintext
--source include/not_embedded.inc
|
|
--source include/master-slave.inc
|
|
--source include/have_binlog_format_mixed.inc
|
|
|
|
#
|
|
# BUG#13427949: CHANGE MASTER TO USER='' (EMPTY USER) CAUSES ERRORS ON VALGRING
|
|
#
|
|
|
|
--connection slave
|
|
call mtr.add_suppression(".*Invalid .* username when attempting to connect to the master server.*");
|
|
|
|
|
|
# Assert that we disallow empty users and that no problem
|
|
--source include/stop_slave.inc
|
|
CHANGE MASTER TO MASTER_USER= '', MASTER_PASSWORD= '';
|
|
START SLAVE;
|
|
--let $slave_io_errno= 1045, 1593
|
|
--source include/wait_for_slave_io_error.inc
|
|
--source include/stop_slave.inc
|
|
|
|
CHANGE MASTER TO MASTER_USER= 'root', MASTER_PASSWORD= '';
|
|
START SLAVE;
|
|
|
|
--source include/rpl_end.inc
|