tripleo-heat-templates/environments/lifecycle/upgrade-prepare.yaml
Jiri Stransky 39321cca71 Update/upgrade prepare/converge in config-download era
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.

Change-Id: I89f54ba9a0a15afd26da4d4b26aba8ef09ebf04b
2018-07-17 20:01:12 +02:00

19 lines
749 B
YAML

# Environment file used in the first step of an overcloud upgrade.
# This file is required by the tripleoclient and not expected to be updated
# by the operator. Please use additional -e env.yaml.
resource_registry:
OS::TripleO::Tasks::*PreConfig: OS::Heat::None
OS::TripleO::Tasks::*PostConfig: OS::Heat::None
parameter_defaults:
UpgradeLevelNovaCompute: auto
UpgradeInitCommonCommand: |
#!/bin/bash
set -eu
yum install -y python-heat-agent-*
yum update -y ansible
yum install -y ansible-pacemaker
# Remove the element os-net-config config.json https://bugs.launchpad.net/tripleo/+bug/1758161/
rm /usr/libexec/os-apply-config/templates/etc/os-net-config/config.json || true
UpgradeRemoveUnusedPackages: false