[2.2, rev5774] Invalid lshw data after upgrade (both rack controller and nodes)
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.
Traceback (most recent call last):
File "/usr/lib/
doc = etree.XML(output)
File "src/lxml/
File "src/lxml/
File "src/lxml/
File "src/lxml/
File "src/lxml/
File "src/lxml/
File "src/lxml/
File "<string>", line None
lxml.etree.
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 772 lines (+359/-180)8 files modifiedsrc/metadataserver/user_data/templates/snippets/maas_run_remote_scripts.py (+2/-51)
src/metadataserver/user_data/templates/snippets/tests/test_maas_run_remote_scripts.py (+0/-115)
src/provisioningserver/refresh/__init__.py (+48/-10)
src/provisioningserver/refresh/maas_api_helper.py (+52/-0)
src/provisioningserver/refresh/node_info_scripts.py (+26/-1)
src/provisioningserver/refresh/tests/test_maas_api_helper.py (+111/-0)
src/provisioningserver/refresh/tests/test_node_info_scripts.py (+26/-3)
src/provisioningserver/refresh/tests/test_refresh.py (+94/-0)
description: | updated |
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 |
For machines the error is similar:
==> /var/log/ maas/maas. log <== processing: [warn] Invalid lshw details: None processing: [warn] Invalid lshw details: None
Mar 2 08:16:45 maas00 maas.tag_
Mar 2 08:16:48 maas00 maas.tag_
^M