tempest

Missing keys in resources.yaml cause early exit in javelin2

Bug #1376185 reported by Chris Dent
6
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.

Chris Dent (cdent)
Changed in tempest:
assignee: nobody → Chris Dent (chdent)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/125320

Changed in tempest:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/125320
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=51e76de9d2053df59d22821ea8182f1255419fd5
Submitter: Jenkins
Branch: master

commit 51e76de9d2053df59d22821ea8182f1255419fd5
Author: Chris Dent <email address hidden>
Date: Wed Oct 1 12:07:14 2014 +0100

    Allow javelin to run with incomplete resources.yaml

    Make it possible to run javelin without all possible keys in
    resources.yaml by starting RES out as a defaultdict(list).

    Closes-Bug: #1376185
    Change-Id: I78520fff501ce0716e5c7c07b435735aa08305d1

Changed in tempest:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.