MariaDB replication tests broken

[Peter Stachowski]

When the binlog_format fix was put in for Percona and MySQL, MariaDB didn't need to be fixed. The scenario test was not set up to handle the differences between the 3 flavors, and needs to be fixed. In a nutshell, MariaDB is expected to have 'STATEMENT' binlog format, not 'MIXED' like the other two.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/320684

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/320684
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=9464300fd6615051936cf8da18cdae0e88f7e43a
Submitter: Jenkins
Branch: master

commit 9464300fd6615051936cf8da18cdae0e88f7e43a
Author: Peter Stachowski <email address hidden>
Date: Tue May 24 17:56:32 2016 -0400

    Fix MariaDB scenario replication test

    When the binlog_format fix was put in for Percona and MySQL,
    (see https://review.openstack.org/#/c/300253 )
    MariaDB didn't need to be fixed. The scenario test was not set
    up to handle the differences between the 3 flavors,
    and has been fixed.

    In a nutshell, MariaDB now expects to have 'STATEMENT' binlog
    format, not 'MIXED' like the other two.

    Change-Id: I1ced565ce18d5492126875c66fb74e85c091e15c
    Closes-Bug: #1585384

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/trove 6.0.0.0b2 development milestone.