tripleo-heat-templates/deployment/haproxy
Damien Ciabrini 7f785e8757 HA: fix <service>_restart_bundle with minor update workflow
For each HA service we have a paunch container <service>_restart_bundle
which is started by paunch whenever config files changes during stack
deploy/update. This container runs a pcs command on a single node to
restart all the service's containers (e.g. all galera on all controllers).
By design, when it is run, configs have already been regenerated by the
deploy tasks on all nodes.

For minor updates, the workflow runs differently: all the steps of the
deploy tasks are run one node after the other, so when
<service>_restart_bundle is called, there is no guarantee that the
service's configs have been regenerated on all the nodes yet.

To fix the wrong restart behaviour, only restart local containers when
running during a minor update. And run once per node. When the minor
update workflow calls <service>_restart_container, we still have the
guarantee that the config files are already regenerated locally.

Co-Authored-By: Michele Baldessari <michele@acksyn.org>
Co-Authored-By: Luca Miccini <lmiccini@redhat.com>

Change-Id: I92d4ddf2feeac06ce14468ae928c283f3fd04f45
Closes-Bug: #1841629
2019-08-30 18:46:31 +02:00
..
haproxy-container-puppet.yaml Stop services for unupgraded controllers 2019-08-07 19:23:11 +02:00
haproxy-internal-tls-certmonger.j2.yaml Request certificate for using host service principals 2019-03-05 10:17:24 +02:00
haproxy-pacemaker-puppet.yaml HA: fix <service>_restart_bundle with minor update workflow 2019-08-30 18:46:31 +02:00
haproxy-public-tls-certmonger.yaml certmonger: Don't restart haproxy on cert renewal 2019-02-01 08:41:32 +02:00
haproxy-public-tls-inject.yaml Fix typo in get container_id ansible task 2019-02-25 12:49:42 +05:30