There is code in tripleo-ansible  which will look at if user
customized the CephAnsiblePlaybook to run and, if so, will always
use that instead of the special playbook we intend to use on
_systemd or _fstobs tags.
This change will reset param value to its default on FFU
prepare so that we actually trigger the special playbooks later
on in the process, whichever custom setting operators might
have set via CephAnsiblePlaybook param for their Queens deployment.
(cherry picked from commit aafb509618)
(cherry picked from commit 8571c5d901)
We inherit the `prepare` commands from deploy, in Rocky we will
automatically get config-download env file there so no need to
explicitly disable DeploymentSteps in *-prepare.yaml files too. We
should also disable the WorkflowSteps in config-download environment,
as they too aren't meant to be used with config-download.
Similarly, for `converge` commands in the *-converge.yaml files we
shouldn't re-enable the DeploymentSteps and WorkflowSteps, as that
would go against using config-download.
So far we haven't been disabling workflows for update/upgrade. We
should disable them by default as they could have the potential to
disrupt the update/upgrade/ffwd procedure.
The main example of a thing we deploy via the workflow resources is
Ceph. We decided no-opping ceph-ansible for the main
update/upgrade/ffwd upgrade steps is the safest path forward and we'll
update/upgrade Ceph it after the main procedure is finished.