Missing keys in resources.yaml cause early exit in javelin2
Bug #1376185 reported by
Chris Dent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Undecided
|
Chris Dent |
Bug Description
If a custom resources.yaml is used with javelin2, and there are missing keys (such as no entry for "volumes") there will be a KeyError and javelin2 will exit.
It would be useful to be able to have some keys unset (or empty) in a provided resources.yaml. Some judicious use of conditionals or a bit of metaprogramming should make this doable.
Changed in tempest: | |
assignee: | nobody → Chris Dent (chdent) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/125320
Review: https:/