mariadb_replication / mysql_replication integration tests: conflicts on centos7

[felixfontein]

SUMMARY

When both the mariadb_replication and mysql_replication tests are run, they fail on CentOS 7 (see here). This moves the mariadb_replication test to POSIX group 2 (the mysql_replication test runs in group 4) to avoid this problem.

Thanks to @Andersson007 for suggesting this.

CC @mattclay

ISSUE TYPE

• Bugfix Pull Request
• Test Pull Request

COMPONENT NAME

mariadb_replication
mysql_replication

[ansibot]

cc @Alexander198961 @Xyon @banyek @bmalynovytch @bmildren @kurtdavis @michaelcoburn @Oneiroi @tolland
click here for bot help

[Andersson007]

Good job, thank you! Will know,
shipit

[felixfontein]

@Andersson007 thanks for helping to fix this :)

[mattclay]

What is the underlying issue with the tests? Using groups to avoid conflicts between tests is a good temporary solution, but not something we should rely on long-term.

[Andersson007]

@mattclay , I recently added CI tests for mysql_replication module to solve all abandoned prs.
As we know, mysql has a lot of forks including MariaDB which has some additional features related to replication.
Therefore, we need both, MySQL and MariaDB.
If we install one of them to a container, it will pull libraries and then we can’t install the other because of conflicts between dependencies.
So it’s not a problem of tests themselves.
I think it is ok to install services to separate containers to avoid conflicts of dependencies.
If it is critical to have both in one container, of course, i could spend (valuable) time trying to clean them up but better I would fix a couple of old abandoned PRs instead :)