[2.5] JS error in machine listing: TypeError: Cannot read property 'filter' of undefined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Björn Tillenius |
Bug Description
This is with MAAS 2.5.1-7489-
I see this error in the machine listing, if I look at the JS console:
TypeError: Cannot read property 'filter' of undefined
It doesn't seem to break the listing completely, since it's seems to work
fine anyway. I also don't see it when I first load the listing. But if I
click on a machine, and the click back to the "Machines" top-level menu item,
I start to see the error.
This is the complete error from the JS console:
angular.
at Scope.scope.
at fn (eval at compile (http://
at Scope.$digest (http://
at Scope.$apply (http://
at http://
at completeOutstan
at http://
Related branches
- Björn Tillenius: Approve
-
Diff: 64 lines (+19/-5)3 files modifiedsrc/maasserver/websockets/handlers/machine.py (+1/-2)
src/maasserver/websockets/handlers/tests/test_controller.py (+1/-1)
src/maasserver/websockets/handlers/tests/test_machine.py (+17/-2)
- Alberto Donato (community): Approve
- MAAS Lander: Needs Fixing
-
Diff: 64 lines (+19/-5)3 files modifiedsrc/maasserver/websockets/handlers/machine.py (+1/-2)
src/maasserver/websockets/handlers/tests/test_controller.py (+1/-1)
src/maasserver/websockets/handlers/tests/test_machine.py (+17/-2)
- MAAS Lander: Needs Fixing
- Björn Tillenius: Disapprove
- Anthony Dillon: Approve
-
Diff: 49 lines (+28/-0)2 files modifiedsrc/maasserver/static/js/angular/directives/machines_table.js (+4/-0)
src/maasserver/static/js/angular/directives/tests/test_machines_table.js (+24/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5.1 |
tags: | added: ui |
Changed in maas: | |
assignee: | nobody → Steve Rydz (steverydz) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Turned out that the problem was in the websocket handler, and not the JS code.