The variable run_tempest was used by validate-tempest. Since now we use
only os_tempest, this variable is no longer required, however, since
use_os_tempest is default to true, we must change it where the
run_tempest is false, like in the upgrade/update jobs, since we don't
run tempest on those.
Change-Id: Idb8166992976ce6303f95f72011aa65fe536931e
Once [0] got merged, there is no chance that the
overcloud-upgrade role will run. Upgrade job have
all been moved to use the new tripleo-upgrade, so
we can dispense all overcloud-upgrade related
variables from the featuresets.
[0] - Iaf30244187d27909ab803175843056e0827d0b24
Change-Id: Ibe715cc4f604ba554db8dd4ab2d95391e4b1f311
deployed_server is no longer common
through out the multinode featuresets.
deploy_steps_ansible_workflow is an
alternative now.
Related-Bug: #1748315
Change-Id: I28988d30338527669da25bc764143cf57a995af9
Use the new upgrade_composable_scenario variable from oooq-extra to set
the composable scenario file used during upgrade.
Closes-Bug: #1714905
Change-Id: Ie0e8de54794a9259c0aeb8c67ae0f6a908844093
This configuration was previously in tripleo-ci in the
testenv/multinode.yml file, but it is not specific to tripleo-ci.
This would be nice to add to the common multinode config and only
override where needed, but our current code does not allow for
overriding what is in the common config.
Change-Id: Ia042fc578ade2c073504ceb117b1da3ff0a4e051
There were still a couple of featuresets that needed
deploy_composable_scenario variable set, and it caused the upgrade CI
job to start failing recently.
As explained in commit message of change
I7e7c13b9151607233f1159ed91c455dcec37e230 we were setting this
variable elsewhere previously, but seems like we aren't doing that
anymore.
Change-Id: I8303a8d90a756512a8cfb0ac23984c58183138a2
Closes-Bug: #1710112
These are the same as featureset011, but each one deploys a different
scenario.
Change-Id: If43370654f28465f25663e06681b712e42a411e6
Depends-On: I36ef3f4edf83ed06a75bc82940152e60f9a0941f