Bug #41072 New mtr fails to start a master/slave system when used with mtr_version=1
Submitted: 27 Nov 2008 14:38 Modified: 20 Jan 2009 10:29
Reporter: Omer Barnir (OCA) Email Updates:
Status: Duplicate Impact on me:
Category:Tests: Server Severity:S3 (Non-critical)
Version:5.1, 6.0 OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any

[27 Nov 2008 14:38] Omer Barnir
When using the new mtr with the backward compatibility flag (mtr_version=1).

The following fails to start a master/slave server:
./mysql-test-run.pl --start-and-exit rpl_alter
(note: any rpl* test can be used as the test is no actually run).
In this case the server fails to start. It seems that internally
a '----binlog-format=row' (note the four dashes) is added to the server 
command line instead of a --binlog-format=row.

How to repeat:
Using the new mtr, set the environment variable mtr_version=1.
run ./mysql-test-run.pl --start-and-exit rpl_alter

Suggested fix:
Fix to have the system started with a master and a slave as done by the 'old' mtr
[20 Jan 2009 10:29] Magnus Blåudd
Fixed by BUG#40742