Websocket doesn't show interface test failure when one iface passes and another fails
Bug #1881361 reported by
Lee Trager
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Lee Trager | ||
2.7 |
In Progress
|
Medium
|
Lee Trager |
Bug Description
I ran the internet connectivity test against two interface. One passed and one failed. The hardware test tab still shows as passed even though the node status is failed testing and the test itself shows as failed testing.
This is because the websocket caching code isn't taking into account that scripts can be run against multiple interfaces.
Related branches
~ltrager/maas:lp1881361_2.8
- Lee Trager (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 109 lines (+82/-1)2 files modifiedsrc/maasserver/websockets/handlers/node.py (+5/-1)
src/maasserver/websockets/handlers/tests/test_machine.py (+77/-0)
~ltrager/maas:lp1881361
Merged
into
maas:master
- Dougal Matthews (community): Approve
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 109 lines (+82/-1)2 files modifiedsrc/maasserver/websockets/handlers/node.py (+5/-1)
src/maasserver/websockets/handlers/tests/test_machine.py (+77/-0)
Changed in maas: | |
milestone: | 2.8.0rc1 → 2.8.0 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 2.8.0 → 2.8.0rc2 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.