Relax-NG validity error : Element hardware failed to validate

[Diogo Matsubara]

As seen OOPS-1782C2286 a parsing error occurred processing hwdb submissions.

There's no traceback or exception raised, only the following logged as the request variables:

    * <oops-message-4>: Parsing submission a288f037ba9baf328477e09c7d3d5cd0: Relax NG validation failed. /tmp/tmpGuSPp3:6 ... Pp3:6780: element hardware: Relax-NG validity error : Element hardware failed to validate content
    * path: /srv/launchpad.net/production/launchpad/cronscripts/process-hwdb-submissions.py
    * script_name: hwdbsubmissions

[Robert Collins (lifeless)]

High per ZOP.

[Ursula Junque (ursinha)]

Updating to Critical according to the updated ZOP

[j.c.sackett (jcsackett)]

This is a result of bad data being send in as a submission.

In lib/lp/hardwardb/scripts/hwdbsubmission.py, @ line 172, we have:

{{{
        if not validator.validate(submission):
            self._logError(
                'Relax NG validation failed.\n%s' % validator.error_log,
                submission_key)
            return None
}}}

The data listed in the OOPS (/59205184/ubuntu.xml.bz2, in the OOPS report) was bad data, so naturally it doesn't validate. We shouldn't be raising an OOPS for this, we should just log it and move on.

[Curtis Hovey (sinzui)]

I reported a bug 746689 in /checkbox about the invalid data.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r12787 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12787>.

[William Grant (wgrant)]

This doesn't break anything, but doesn't seem to fix the bug. See OOPS-1927QS260 for an example of the continued OOPSing.

[Abel Deuring (adeuring)]

This is the same as bug 835103, which was fixed in r13822 and r13870