Damien Ciabrini e965239d60 Ensure redis_tls_proxy starts after all redis instances ... When converting a HA control plane to TLS-e, 1) the bootstrap node tells pacemaker to restart all redis instances to take into account the new TLS-e config; 2) a new container redis_tls_proxy is started on every controller to encapsulate redis traffic in TLS tunnels. This happens during step 2. Redis servers have to be restarted everywhere for redis_tls_proxy to be able to start tunnels properly. Since we can't guarantee that across several nodes during the same step, tweak the startup of redis_tls_proxy instead; make sure to only create the tunnels once the targeted host:port can be bound (i.e. redis was restarted). Change-Id: I70560f80775dacddd82262e8079c13f86b0eb0e6 Closes-Bug: #1883096 (cherry picked from commit b91a1a09cb)		2020-07-27 15:50:27 +00:00
..
mysql-base.yaml	Support for mariadb's ed25519 authentication	2020-04-18 09:36:10 +00:00
mysql-client.yaml	flatten database service MySQL Client	2019-01-30 09:38:32 -05:00
mysql-container-puppet.yaml	Add mode option when creating persistent directories.	2020-05-15 20:41:12 +00:00
mysql-pacemaker-puppet.yaml	Check transfer data flag to skip pacemaker normal upgrade.	2020-06-04 14:25:14 +02:00
redis-base-puppet.yaml	Force redis::ulimit to be an integer	2019-11-27 23:16:15 +00:00
redis-container-puppet.yaml	Remove /run from some services	2020-07-20 18:55:44 +00:00
redis-pacemaker-puppet.yaml	Ensure redis_tls_proxy starts after all redis instances	2020-07-27 15:50:27 +00:00