Merge lp:~gmb/maas-test/report-machine-info into lp:maas-test
Proposed by
Graham Binns
Status: | Merged |
---|---|
Approved by: | Graham Binns |
Approved revision: | 135 |
Merged at revision: | 124 |
Proposed branch: | lp:~gmb/maas-test/report-machine-info |
Merge into: | lp:maas-test |
Diff against target: |
49 lines (+24/-0) 2 files modified
maastest/maasfixture.py (+12/-0) maastest/tests/test_maasfixture.py (+12/-0) |
To merge this branch: | bzr merge lp:~gmb/maas-test/report-machine-info |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Review via email: mp+201395@code.launchpad.net |
Commit message
Include a dump of lshw info from the commissioned node with the test log.
Description of the change
This branch adds a dump of the MAAS DB as an attachment to the blob generated by maas-test. We can use this to help us get more information about failures. In future we can extract data from this dump and use it in the bug report to help Launchpad de-dupe, but for now this is a good start.
To post a comment you must log in.
I might be missing something but why didn't you do something similar to what we did with MAASFixture. collect_ logs and leverage the addDetail/fixture cleanup combination… i.e. something along the lines of http:// paste.ubuntu. com/6744843/ ? It seems a bit simpler to me.