Bug 689338

Summary: [RFE] libxml2 RelaxNG validation messages are confusing, consider switching to different library
Product: [Retired] Beaker Reporter: Marian Ganisin <mganisin>
Component: lab controllerAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 0.6CC: bpeck, mcsontos, stl, tools-bugs
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: UX
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-21 14:13:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marian Ganisin 2011-03-21 06:58:35 UTC 
Description of problem:
If I try to clone this:
https://beaker.engineering.redhat.com/jobs/63966

it doesn't work, following error messages are printed:

Job failed schema validation. Please confirm that you want to submit it.

    * Line 0, col 0: Extra element partitions in interleave
    * Line 6, col 0: Invalid sequence in interleave
    * Line 6, col 0: Element recipe failed to validate content
    * Line 5, col 0: Element recipeSet failed to validate content

This is not helpful message. After few attempts I found possible reason, it could be missing fs="" attribute of tag partition, with that cloning was successful.

Error message could be little bit more descriptive.
Comment 1 Raymond Mancy 2011-03-21 07:13:50 UTC 
I think that's just the kind of vitriol relax ng spews. The real problem is why cloning a job produces XML that does not pass validation.
Comment 2 Dan Callaghan 2011-03-21 07:29:12 UTC 
Just to expand on comment 1: Beaker is using libxml2 (via lxml) for RELAX NG validation. It is that library which produces these errors. I agree the error messages are often confusing, but there is nothing we can do on the Beaker side to make them any friendlier, short of switching validator implementations or writing a patch for libxml2.
Comment 4 Roman Joost 2015-11-12 05:26:51 UTC 
Dear Marian,

does this problem still happen now and then?
Comment 5 Dan Callaghan 2015-11-13 05:38:23 UTC 
libxml2's RELAX NG validation has not got any smarter, the error messages are still highly inscrutable.
Comment 6 Tomas Klohna 🔧 2019-04-04 17:29:50 UTC 
Changing this issue to RFE, agreed that the validation messages are confusing and not helpful.