From 852e0329a76e4436427e1f59b278441f9b8dc5fe Mon Sep 17 00:00:00 2001 From: Antony Messerli Date: Mon, 6 Aug 2018 15:07:14 -0500 Subject: [PATCH] Remove hardening from leap upgrades In order to reduce time to run and avoid complexities from older environments that may have specific requirements or devations from recommended practices, disable the hardening play during the leap upgrades. If security-hardening is desired, the recommendation for operators is to run hardening after the upgrade has completed. Change-Id: I85865a39e84e65ac211c1077f484bf008673c840 --- leap-upgrades/re-deploy.sh | 7 ------- 1 file changed, 7 deletions(-) diff --git a/leap-upgrades/re-deploy.sh b/leap-upgrades/re-deploy.sh index 31aba3d4..84960609 100755 --- a/leap-upgrades/re-deploy.sh +++ b/leap-upgrades/re-deploy.sh @@ -52,13 +52,6 @@ fi # Setup Hosts RUN_TASKS+=("openstack-hosts-setup.yml -e redeploy_rerun=true") -# Run the security-hardening playbook in redeployment -if [[ -n "${SKIP_HARDENING_TAGS}" ]]; then - RUN_TASKS+=("security-hardening.yml --skip-tags=${SKIP_HARDENING_TAGS}") -else - RUN_TASKS+=("security-hardening.yml") -fi - # Ensure the same pip everywhere, even if requirement met or above RUN_TASKS+=("${UPGRADE_UTILS}/pip-unify.yml -e release_version=\"${NEWTON_RELEASE}\"")