[2.6, events] Test events don't have details at all
Bug #1828633 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Newell Jensen | ||
Bug Description
The events for the tests shown as INFO don't have proper details, e.g:
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate
The machine has 5 disks, and the logs above match one per disk, so the events should shown which disk is being tested, e.g:
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate on sda
Fri, 10 May. 2019 22:10:19 Running test - smartctl-validate on sdb
Related branches
~newell-jensen/maas:lp1828633
- Blake Rouse (community): Approve
-
Diff: 97 lines (+42/-4)2 files modifiedsrc/maasserver/models/signals/scriptresult.py (+6/-1)
src/maasserver/models/signals/tests/test_scriptresult.py (+36/-3)
| tags: | added: events |
| Changed in maas: | |
| milestone: | none → 2.6.0rc1 |
| assignee: | nobody → Newell Jensen (newell-jensen) |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
