Ticket #1067 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

bcfg2-repo-validate throws up on missing aligator

Reported by: rcuza Owned by:
Priority: major Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-server Version: 1.0
Keywords: Cc:


On the malformed attached Metadata/groups.xml file, bcfg2.repo.validate throws up the following error:

# bcfg2-repo-validate 
Traceback (most recent call last):
  File "/usr/sbin/bcfg2-repo-validate", line 40, in <module>
    xdata = lxml.etree.parse("%s/Metadata/groups.xml" % repo)
  File "lxml.etree.pyx", line 2706, in lxml.etree.parse (src/lxml/lxml.etree.c:49958)
  File "parser.pxi", line 1500, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:71797)
  File "parser.pxi", line 1529, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:72080)
  File "parser.pxi", line 1429, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:71175)
  File "parser.pxi", line 975, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:68173)
  File "parser.pxi", line 539, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:64257)
  File "parser.pxi", line 625, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:65178)
  File "parser.pxi", line 565, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:64521)
lxml.etree.XMLSyntaxError: expected '>', line 13, column 1

The expected behaviour is for bcfg2-repo-validate to say "Yo phat fingers, you are missing a '>' on line 12. What were you thinking?"


groups.xml (651 bytes) - added by rcuza 12 years ago.
Malformed Metadata/groups.xml file

Change History

Changed 12 years ago by rcuza

Malformed Metadata/groups.xml file

comment:1 Changed 12 years ago by

  • Owner changed from desai to
  • Status changed from new to accepted

comment:2 Changed 12 years ago by

  • Status changed from accepted to closed
  • Resolution set to fixed
  • Milestone changed from Bcfg2 1.2.1 Release (Bugfix) to Bcfg2 1.2.0 Release

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.