Add missing deploy_composable_scenario in featuresets

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
This commit is contained in:
Jiri Stransky 2017-08-11 11:07:42 +02:00 committed by Emilien Macchi
parent bf6ac007b1
commit 3fa2214be9
5 changed files with 5 additions and 0 deletions

View File

@ -34,6 +34,7 @@ test_ping: false
run_tempest: false
step_introspect: false
deploy_composable_scenario: true
composable_scenario: multinode-containers.yaml
# options below direct automatic doc generation by tripleo-collect-logs

View File

@ -34,6 +34,7 @@ test_ping: false
run_tempest: false
step_introspect: false
deploy_composable_scenario: true
composable_scenario: scenario001-multinode-containers.yaml
# options below direct automatic doc generation by tripleo-collect-logs

View File

@ -34,6 +34,7 @@ test_ping: false
run_tempest: false
step_introspect: false
deploy_composable_scenario: true
composable_scenario: scenario002-multinode-containers.yaml
# options below direct automatic doc generation by tripleo-collect-logs

View File

@ -34,6 +34,7 @@ test_ping: false
run_tempest: false
step_introspect: false
deploy_composable_scenario: true
composable_scenario: scenario003-multinode-containers.yaml
# options below direct automatic doc generation by tripleo-collect-logs

View File

@ -34,6 +34,7 @@ test_ping: false
run_tempest: false
step_introspect: false
deploy_composable_scenario: true
composable_scenario: scenario004-multinode-containers.yaml
# options below direct automatic doc generation by tripleo-collect-logs