2.x Fix MariaDB in automatic tests

[gchtr]

Issue

Tests don’t run after automatic update to MariaDB v11.

Solution

As a first measure: downgrade to MariaDB v10.

Then, we can start to find out what went wrong. I read the Upgrade Guide for the 11 release (https://mariadb.com/kb/en/upgrading-from-mariadb-10-11-to-mariadb-11-0/), but I don’t know MariaDB or MySQL well enough to see what we would need to change.

@nlemoine Do you know what to do here?

Impact

Fixes automatic tests.

Usage Changes

None.

Considerations

None.

[Levdbas]

This is what we might need to fix this for MariaDB 11: See this PR.
I think we need to change the --health-cmd line in our test and maybe set those two constants as well? @gchtr

This change is needed because of:

11.0, unlike previous version, no longer includes mysql named compatible executable symlinks inside the container.

[gchtr]

Cool, thanks for finding the solution. In the thread of that PR, I found a link to a blog post that contains even a simpler solution: https://mariadb.org/mariadb-server-docker-official-images-healthcheck-without-mysqladmin/.

Looks like the tests are not stuck on the MySQL health check anymore. So I’m merging this in.