Comment 8 for bug 1721497

I think the correct thing to do is to revert https://review.openstack.org/#/c/497766/

It clearly would have failed the scenario004 job, but that job did not run and is now broken.

The passed-ci-test tag on dockerhub is/was just there as some testing of the new pipeline and the full set of containers with that tag have not actually passed the CI pipeline.

If we dont want to revert the patch that actually broke this...the only other option is to just manually tag a new mariadb container that has not passed the promote CI with everything else. This seems fine(ish) for the current issue, but is a pretty bad habit to carry forward.