Jiri Stransky f8ca0d41ad Reintroduce upgrade tasks for stopping pacemaker cluster ... It is likely that change I50a1289a864f804d02a2e2bc0ca8738a186beff0 broke upgrade CI, even though the job somehow passed on it. MariaDB upgrade tasks now cannot remove the container image, because it's being used by a running container. Let's keep all tasks for stopping Pacemaker cluster for now, both untagged ones and the ones tagged for system_upgrade_prepare step. Change-Id: Ic45b74c83b99dc58cd6e0f0f45d421b88c7e97a1 Closes-Bug: #1831022		2019-05-30 07:35:27 +00:00
..
clustercheck-container-puppet.yaml	Move containers-common.yaml into deployment	2019-04-14 18:15:12 -04:00
pacemaker-baremetal-puppet.yaml	Reintroduce upgrade tasks for stopping pacemaker cluster	2019-05-30 07:35:27 +00:00
pacemaker-remote-baremetal-puppet.yaml	Move pacemaker, pacemaker-remote into deployments	2019-04-22 20:54:13 -04:00