maas-test needs better logging
Bug #1260025 reported by
Jeff Lane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| maas-test |
Fix Committed
|
Low
|
Raphaël Badin | ||
Bug Description
since maas-test is so new, it needs a couple things to help with debugging.
1: it needs debug as a log level with the option to turn this on and off via a switch like --verbose or -v
The INFO level logs are good so far, I think, but perhaps they can be more verbose for sorting out what's going on as a test runs, and informing the user of exactly what data is being used or passed back and forth, where and what images and files are being downloaded, etc.
2: it would be useful to also save these to a log file without needing to resort to console redirection trickery. something like a --log switch followed by a file name that would tell maas-test to log both to the console and the log file (this would be especially helpful for debug purposes)
Related branches
lp:~rvb/maas-test/fix-error-reporting
- Gavin Panella (community): Approve
-
Diff: 59 lines (+9/-11)2 files modifiedmaastest/kvmfixture.py (+4/-3)
maastest/tests/test_kvmfixture.py (+5/-8)
Revision history for this message
| Raphaël Badin (rvb) wrote | #1 |
| Changed in maas-test: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in maas-test: | |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Triaged → Fix Committed |
To post a comment you must log in.
1: I hope to improve the situation by adding all the relevant MAAS logs into the output when a test fails.
2: we're still working on how to report the result of a test run. The default mechanism will be to upload the result to launchpad but we intend to provide a way to store the result in a file as well.