openstack/openstack-ansible-ops
Code Issues Proposed changes

Prevent deploying old code once leaped

Browse Source 
Previously the operator could choose to leap from old
code once the code to leap to had been deployed. This
would cause things to break as it would attempt to
run the older version code on top of the newly deployed
leaped code.

This identifies those conditions, alerts the operator
and calls the resume_incompete_leap instead of asking
the operator to input the release to upgrade from
again.

Change-Id: I928bf7e6db88d46617af800692e9b76a6bcc1ba8
This commit is contained in:
Antony Messerli 2017-11-01 17:44:06 -05:00
parent 169b475168
commit 71fd2f6b7f
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
leap-upgrades/lib/functions.sh
View File

@ -313,6 +313,12 @@ function pre_flight {
set_upgrade_vars
if [[ -f "${CONFIG_DIR}/upgrade-leap/redeploy-started.complete" && ! -f "${CONFIG_DIR}/upgrade-leap/osa-leap.complete" ]]; then
warning "Redeploy of ${CODE_UPGRADE_FROM} started but did not complete..."
resume_incomplete_leap
elif [[ -f "/opt/leap42/openstack-ansible-upgrade-hostupgrade.leap" ]] ; then
warning "Current code deployed is ${CODE_UPGRADE_FROM}"
warning "and it appears the leap process was interrupted after"
warning "starting the deployment of ${CODE_UPGRADE_FROM}."
resume_incomplete_leap
elif [ "${VALIDATE_UPGRADE_INPUT}" == "TRUE" ]; then
validate_upgrade_input