MariaDB fails while scaling out

[Dincer Celik]

Using stable/stein and some handler tasks fails the deployment while trying to scale out control nodes. Seems the tasks are running despite there's no mariadb container there. I'm attaching the log for scaling out from 3 to 7.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/677453
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=074d254b0891f9648de9ef8b982a3555e8c1f036
Submitter: Zuul
Branch: stable/stein

commit 074d254b0891f9648de9ef8b982a3555e8c1f036
Author: Mark Goddard <email address hidden>
Date: Tue Aug 20 12:39:44 2019 +0100

    Don't stop mariadb slaves if they aren't running

    Stein only

    If mariadb is not running on all of the slave nodes during a deploy,
    reconfigure or upgrade, then currently the "remove restart policy from
    slave mariadb" handler will fail on nodes where the container does not
    exist. A valid use case for this is when scaling out the cluster, but it
    could also happen if the slaves are down for some other reason.

    This change checks if the mariadb container exists on slaves, and skips
    all shutdown related tasks on slaves where it does not.

    Change-Id: I9a191da0ec6ac13ec6dd882b1723d3686f9edc8c
    Closes-Bug: #1840764

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 8.0.1 release.