Jiri Stransky 4b9c3637f8 Force re-run of pacemaker bundle init containers during upgrade-scaleup ... We need to recreate the *_init_bundle containers during the staged upgrade (upgrade-scaleup), because the init containers will e.g. set the correct replica count for the bundle as we're scaling up from 1 to 3 controllers. The init containers wouldn't get re-run/recreated automatically on upgrade-scaleup because none of their input would change. The DeploymentIdentifier is set by the `openstack upgrade prepare` command and applied during upgrade with `--limit controller-0`. Then later when we run `--limit controller-0,controller-1`, the DeploymentIdentifier value does not change from the perspective of controller-0, so we have to explicitly remove the bundle init containers to force re-running them. Change-Id: I93c6d7292f37529735e24286f4076634aa4fe6a5 Partial-Bug: #1831690 (cherry picked from commit d4db2fa532)		2019-08-17 07:56:02 +00:00
..
haproxy-container-puppet.yaml	Stop services for unupgraded controllers	2019-07-16 15:24:04 +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	Force re-run of pacemaker bundle init containers during upgrade-scaleup	2019-08-17 07:56:02 +00: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