[2.2, rev5774] Invalid lshw data after upgrade (both rack controller and nodes)

Bug #1669428 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Lee Trager

Bug Description

After upgrade from rev5773 to rev5774, there's an error processing lshw output for the rack controller.

2017-03-02 08:07:57 metadataserver.builtin_scripts.hooks: [error] Invalid lshw data.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/metadataserver/builtin_scripts/hooks.py", line 187, in update_hardware_details
    doc = etree.XML(output)
  File "src/lxml/lxml.etree.pyx", line 3192, in lxml.etree.XML (src/lxml/lxml.etree.c:82678)
  File "src/lxml/parser.pxi", line 1819, in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:124533)
  File "src/lxml/parser.pxi", line 1707, in lxml.etree._parseDoc (src/lxml/lxml.etree.c:123074)
  File "src/lxml/parser.pxi", line 1079, in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:117114)
  File "src/lxml/parser.pxi", line 573, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:110510)
  File "src/lxml/parser.pxi", line 683, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:112276)
  File "src/lxml/parser.pxi", line 624, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:111367)
  File "<string>", line None
lxml.etree.XMLSyntaxError: <no detail available>

Related branches

Revision history for this message
Andres Rodriguez (andreserl) wrote :

For machines the error is similar:

==> /var/log/maas/maas.log <==
Mar 2 08:16:45 maas00 maas.tag_processing: [warn] Invalid lshw details: None
Mar 2 08:16:48 maas00 maas.tag_processing: [warn] Invalid lshw details: None
^M

Changed in maas:
assignee: nobody → Lee Trager (ltrager)
milestone: none → 2.2.0
importance: Undecided → High
status: New → Confirmed
importance: High → Critical
description: updated
Revision history for this message
Blake Rouse (blake-rouse) wrote :

Lee,

Are you 100% sure your processing only the stdout for the commissioning hooks? Seems like that might not be the case.

summary: - [2.2, rev5774] Invalid lshw data after upgrade
+ [2.2, rev5774] Invalid lshw data after upgrade (both rack controller and
+ nodes)
Changed in maas:
status: Confirmed → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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