Jiri Stransky f5ffc4d4c7 Fix MariaDB staged upgrade ... This patch fixes 2 issues on MariaDB staged upgrade: * After we landed service stopping on the data transfer step, the actual MariaDB staged upgrade moved from step 1 to step 2 of external_upgrade_tasks, but we only ran steps 0 and 1 during the upgrade. Increase the number of steps to run step 2 as well. * The mysql_upgrade container was being re-run on each upgrade-scaleup even on nodes where it already ran before and MariaDB was already running there, conflicting with the upgrade container. We fix this by only running the MariaDB upgrade if there's no MariaDB running yet on the particular node. Change-Id: I2feba6c22cdf07ea6af406c5edd27f62ff285d87 Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com> Closes-Bug: #1841415 (cherry picked from commit 22f26d7a94)		2019-08-27 13:43:00 +00:00
..
services	Make krb-service-principal metadata per-Role	2019-04-05 14:22:20 +00:00
container-puppet.py	Re-Add facter cache for container configurations	2019-07-22 07:57:13 -06:00
deploy-steps-tasks.yaml	Force "Pre-cache" tasks to run in dry run	2019-08-09 09:29:57 -04:00
deploy-steps.j2	Fix MariaDB staged upgrade	2019-08-27 13:43:00 +00:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00