galera service has a hardcoded start timeout

[Damien Ciabrini]

In a HA control plane, the galera service is allowed at most 300 seconds to start on a node and to joins an existing galera cluster.

While in the vast majority of cases this is largely sufficient due to how much data an OpenStack cloud stores in the galera cluster, sometimes it's desirable to have a longer timeout.

For instance, on very large clouds, or on slow machines, it may happen that a full DB synchronization transfer gigabytes of data across the network, and sometimes it takes more than the allowed 300s to finish.

We'd need a way to configure that timeout in TripleO.

[Bogdan Dobrelya (bogdando)]

This is probably related to another very similar issue https://bugs.launchpad.net/fuel/+bug/1580159

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/736135
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=0606e22e245761f66baff3eb8846473d2eab5be3
Submitter: Zuul
Branch: master

commit 0606e22e245761f66baff3eb8846473d2eab5be3
Author: Damien Ciabrini <email address hidden>
Date: Wed Jun 17 10:58:01 2020 +0200

    Make promote timeout configurable

    Allow override of galera promote timeout

    This commit removes the hard coded value of pacemaker promote time out
    (currently 300s), and allows operators to override it via:

    tripleo::profile::pacemaker::database::mysql::promote_timeout
    tripleo::profile::pacemaker::database::mysql_bundle::promote_timeout

    Closes-Bug: #1883896
    Change-Id: I96f5d349b94f05f4f66db6b85ba481deba0015d9

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/737996

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/737996
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=9b02574d3a4e5566abd75b992a5078bc9cee2e32
Submitter: Zuul
Branch: stable/ussuri

commit 9b02574d3a4e5566abd75b992a5078bc9cee2e32
Author: Damien Ciabrini <email address hidden>
Date: Wed Jun 17 10:58:01 2020 +0200

    Make promote timeout configurable

    Allow override of galera promote timeout

    This commit removes the hard coded value of pacemaker promote time out
    (currently 300s), and allows operators to override it via:

    tripleo::profile::pacemaker::database::mysql::promote_timeout
    tripleo::profile::pacemaker::database::mysql_bundle::promote_timeout

    Closes-Bug: #1883896
    Change-Id: I96f5d349b94f05f4f66db6b85ba481deba0015d9
    (cherry picked from commit 0606e22e245761f66baff3eb8846473d2eab5be3)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/train
Review: https://review.opendev.org/742376

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/742376
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=2a16409d227134d6797b911eb883895489ca500b
Submitter: Zuul
Branch: stable/train

commit 2a16409d227134d6797b911eb883895489ca500b
Author: Damien Ciabrini <email address hidden>
Date: Wed Jun 17 10:58:01 2020 +0200

    Make promote timeout configurable

    Allow override of galera promote timeout

    This commit removes the hard coded value of pacemaker promote time out
    (currently 300s), and allows operators to override it via:

    tripleo::profile::pacemaker::database::mysql::promote_timeout
    tripleo::profile::pacemaker::database::mysql_bundle::promote_timeout

    Closes-Bug: #1883896
    Change-Id: I96f5d349b94f05f4f66db6b85ba481deba0015d9
    (cherry picked from commit 0606e22e245761f66baff3eb8846473d2eab5be3)
    (cherry picked from commit 9b02574d3a4e5566abd75b992a5078bc9cee2e32)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-tripleo 11.5.0 release.