diff options
| author |   Markos Chandras <mchandras@suse.de> | 2018-03-22 10:08:03 +0000 |
|---|---|---|
| committer | Markos Chandras <mchandras@suse.de> | 2018-03-22 10:08:33 +0000 |
| commit | 47ec2e605fb9516ddd46d9aa723318fdb296f2f2 (patch) | |
| tree | 67f15d8d553420f29bed516a31dee3d1243ead55 /xci | |
| parent | 8cb2bc0cdf0565ce59546b1ec2aac513fb7fecaa (diff) | |
xci: playbooks: Fix message on fail task for deployed scenario
The fail message was a bit weird since it listed all the scenarion
information as below:
TASK [Fail if {'scm': u'git', 'src':
u'https://git.opnfv.org/releng-xci', 'scenario': u'os-nosdn-nofeature',
'installers': [{'flavors': [u'ha', u'mini', u'noha'], 'installer':
u'osa', 'distros': [u'opensuse', u'ubuntu', u'centos']}], 'version': u'master', 'role':
u'xci/scenarios/os-nosdn-nofeature/role/os-nosdn-nofeature'} is not
supported] ***
skipping: [localhost]
This looks awkward and we should only list the actual scenario name
instead.
Change-Id: I725793f91661f00606573906847336716fecd418
Signed-off-by: Markos Chandras <mchandras@suse.de>
Diffstat (limited to 'xci')
| -rw-r--r-- | xci/playbooks/get-opnfv-scenario-requirements.yml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/xci/playbooks/get-opnfv-scenario-requirements.yml b/xci/playbooks/get-opnfv-scenario-requirements.yml index 6937b47e..d133048a 100644 --- a/xci/playbooks/get-opnfv-scenario-requirements.yml +++ b/xci/playbooks/get-opnfv-scenario-requirements.yml @@ -123,11 +123,11 @@ - deploy_scenario_flavor when: deploy_scenario is defined - - name: Fail if {{ deploy_scenario }} is not supported + - name: Fail if {{ deploy_scenario.scenario }} is not supported fail: msg: - ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ - - ERROR! The {{ deploy_scenario }} scenario can't be deployed. This is because + - ERROR! The {{ deploy_scenario.scenario }} scenario can't be deployed. This is because - the {{ installer_type }} XCI installer or the {{ xci_flavor }} flavor or the {{ xci_distro }} - distribution is not supported by this scenario. It may also be possible that - this scenario doesn't exist at all or it's not listed in {{ scenario_file }}. |