Bogdan Dobrelya 810b81991f Do not fail if haproxy container UUID changes ... There is a possibility that haproxy container crashed and restarted with another UUID, while the deployment is trying to reload it after reconfiguring the certificates, by sending a `kill -HUP <uuid-of-the-container>`. In that case, ingore errors for the commands block, since there is no longer need to reload the newly created container. Related rhbz#1973674 Change-Id: I4b40d73ab329dc219ee7a387201b0747a6233ed4 Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>		2021-07-26 11:07:11 +00:00
..
haproxy-container-puppet.yaml	Use server side env merging for ServiceNetMap/VipSubnetMap	2021-05-19 10:16:58 +05:30
haproxy-edge-container-puppet.yaml	Drop usage of removed tripleo::haproxy parameters	2021-06-04 23:26:19 +09:00
haproxy-internal-tls-certmonger.j2.yaml	Use server side env merging for ServiceNetMap/VipSubnetMap	2021-05-19 10:16:58 +05:30
haproxy-pacemaker-puppet.yaml	Use server side env merging for ServiceNetMap/VipSubnetMap	2021-05-19 10:16:58 +05:30
haproxy-public-tls-certmonger.yaml	Use server side env merging for ServiceNetMap/VipSubnetMap	2021-05-19 10:16:58 +05:30
haproxy-public-tls-inject.yaml	Do not fail if haproxy container UUID changes	2021-07-26 11:07:11 +00:00