HA: DB root password update does not get reflected in running container

[Damien Ciabrini]

With the rework of HA container management on the host [1], we
split the execution of puppet in two different runs. One runs on
the host to update and restart pacemaker resource (bundle), the
other runs in the container and is responsible for creating or
updating mysql users.

The problem with the rework is that for technical reasons, the
puppet runs on the host must be executed prior to the one
in the container. As a result, if the DB root password is updated
in the second puppet run, the container is never restarted to pick
up the new root password, and the running galera container is left
with an old mysql root password file.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/828370

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/828370
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/7f8876ce7c4fc1a4a22afe5316304aaedb40d3b7
Submitter: "Zuul (22348)"
Branch: master

commit 7f8876ce7c4fc1a4a22afe5316304aaedb40d3b7
Author: Damien Ciabrini <email address hidden>
Date: Tue Feb 8 16:38:49 2022 +0100

    Sync updated DB root password in running container

    Now that pacemaker resources are managed by puppet on
    the host [1], the galera container gets restarted
    before the puppet run that manages password update.
    To make sure that any DB root password update gets
    reflected in the running galera container, add a
    deploy task that syncs up .myc.cnf if required.

    Closes-Bug: #1960332

    [1] Ie14819b66cecdb5a9cc6299b68a0cc70a7aa3370

    Change-Id: I60f73939dac03b14389f37e5ffc67de5d929ee52

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 16.0.0 release.