openstack/openstack-ansible-ops
Code Issues Proposed changes

Stop building a newton venv for LEAP upgrades

Browse Source 
Because "newton" is the last release LEAP upgrades are compatible with
there's no need to build a migration venv for newton. All of the newton
specific migrations will be run during the redeployment phase so this
venv has no specific purpose and is simply prolonging an already long
maintenance.

Change-Id: I06f23ed3bfdca5f1d5d56cb9fabd53cab01b83b6
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter 2018-01-03 14:46:45 -06:00
parent dded86cf84
commit e24ef8d57c
No known key found for this signature in database
GPG Key ID: 9443251A787B9FB3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
leap-upgrades/prep.sh
View File

@ -34,7 +34,7 @@ for RELEASES in ${TODO}; do
RELEASE_NAME=${RELEASES}_RELEASE
if [[ ! -f "/opt/leap42/openstack-ansible-${!RELEASE_NAME}-prep.leap" ]]; then
clone_release ${!RELEASE_NAME}
if [[ "${RELEASES}" != "JUNO" ]]; then
if [[ "${RELEASES}" != "JUNO" ]] || [[ "${RELEASES}" != "NEWTON" ]]; then
get_venv ${!RELEASE_NAME}
fi
touch "/opt/leap42/openstack-ansible-${!RELEASE_NAME}-prep.leap"