[2.2, 2.3] MAAS doesn't filter out progress bars, spinners, and counters from scripts making logs difficult to read
Bug #1705792 reported by
Lee Trager
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Lee Trager | ||
| 2.2 |
Fix Released
|
High
|
Lee Trager | ||
| 2.3 |
Fix Released
|
High
|
Lee Trager | ||
Bug Description
During commissioning and testing MAAS runs scripts and captures its data. The scripts may use commands which do not detect they are not being run in a terminal and show progress bars, counters, or spinners. These effects are captured by MAAS making the log more difficult to read. apt has a known bug[1] causing MAAS to log "Read database ... x%" anytime apt is used. The memtester script outputs a spinner making its output impossible to read.
[1] https:/
Related branches
~ltrager/maas:emulate_terminal_2.2
- Lee Trager (community): Approve
-
Diff: 96 lines (+59/-4)2 files modifiedsrc/provisioningserver/refresh/maas_api_helper.py (+41/-4)
src/provisioningserver/refresh/tests/test_maas_api_helper.py (+18/-0)
~ltrager/maas:emulate_terminal
- Newell Jensen (community): Approve
-
Diff: 96 lines (+59/-4)2 files modifiedsrc/provisioningserver/refresh/maas_api_helper.py (+41/-4)
src/provisioningserver/refresh/tests/test_maas_api_helper.py (+18/-0)
| Changed in maas: | |
| milestone: | none → 2.3.0 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
