openstack/ironic
Code Issues Proposed changes

grenade: For multi-node grenade, do not upgrade nova

Browse Source 
Multi-node grenade jobs will fail if we upgrade nova as the minimum
required API for nova to communicate with ironic was upgraded.

Our goal for multi-node grenade is to test rolling upgrades. The
scenario we envision for rolling upgrades to be done is:

 1) Upgrade ironic-conductor services one by one. This means old
    ironic-api services communicating with new and old
    ironic-conductor services. This is what the multi-node grenade job
    tests.
 2) Upgrade ironic-api services.
 3) Upgrade nova

In this upgrade procedure we should not be running updated nova with
old ironic-api services. This patch fixes that.

Closes-Bug: #1706418
Change-Id: I85c607ae7d031e4cabcb505915aca7e88df166aa
This commit is contained in:
John L. Villalovos 2017-07-25 14:33:29 -07:00
parent 3d570738ef
commit 9d161f6922
1 changed files with 6 additions and 0 deletions

6
devstack/upgrade/settings

@ -22,3 +22,9 @@ source $BASE_TOP_DIR/lib/keystone
# Update global variables like DEFAULT_IMAGE_NAME that are set in ironic devstack plugin
IRONIC_BASE_DEVSTACK_DIR=$BASE_TOP_DIR/../ironic/devstack
source $IRONIC_BASE_DEVSTACK_DIR/lib/ironic
# NOTE(jlvillal): For multi-node grenade jobs we do not want to upgrade Nova
if [[ "${HOST_TOPOLOGY}" == "multinode" ]]; then
# Remove 'nova' from the list of projects to upgrade
UPGRADE_PROJECTS=$(echo $UPGRADE_PROJECTS | sed -e 's/\s*nova//g' )
fi