Description of problem: Using attached job xml results in failure during validation of xml. The problem is guestname attribute that is required. <guestrecipe guestargs="--hvm"> </guestrecipe> This results in: WARNING: job xml validation failed: Invalid sequence in interleave Adding guestname arg (even empty) resolves the issue. <guestrecipe guestname="" guestargs="--hvm"> </guestrecipe> Version-Release number of selected component (if applicable): beaker-client-0.5.63-1.fc14.noarch How reproducible: Everytime, using the attached xml. Actual results: Failed to submit job using bkr command line tool. Expected results: Job defined in xml file is submitted.
Created attachment 488370 [details] job xml
To be more precise it results in: WARNING: job xml validation failed: Invalid sequence in interleave <Fault 1: 'exceptions.KeyError:'> The warning itself is harmless and in this case it pinpoints the problem - the KeyError message does not help much.
Bulk reassignment of issues as Bill has moved to another team.
Note that if the guestname is not supplied (ignoring the validation errors) it will appear in the recipe XML (and therefore to beah and /distribution/virt/install) as the literal 'None' which can lead to duplicate guest names in a multihost test.
Dan, given the changes to guest recipes in 0.10, isn't this a fairly trivial fix now?
Yes we can support empty guestname easily. There are obviously lots of people using it in spite of the validation warnings (e.g. bug 880983). There are probably just two things needed here: updating the RELAX NG schema to make the guestname attribute optional, and making sure when it is omitted that we store and return sensible values everywhere ("" instead of "None" as in comment 4).
On Gerrit: http://gerrit.beaker-project.org/#/c/1666/
Beaker 0.12 has been released.