Comment 2 for bug 1840764

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/stein)

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