[2.5] JS error in machine listing: TypeError: Cannot read property 'filter' of undefined

Bug #1811377 reported by Björn Tillenius
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Björn Tillenius

Bug Description

This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 with RBAC enabled.

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.js?v=2.5.1(7…0ubuntu1~18.04.1):6 TypeError: Cannot read property 'filter' of undefined
    at Scope.scope.removeDuplicates (http://10.0.8.86:5240/MAAS/static//js/bundle/maas-min.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):1:1043610)
    at fn (eval at compile (http://10.0.8.86:5240/MAAS/combo/angular.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):7:11337), <anonymous>:4:402)
    at Scope.$digest (http://10.0.8.86:5240/MAAS/combo/angular.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):8:19723)
    at Scope.$apply (http://10.0.8.86:5240/MAAS/combo/angular.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):8:22211)
    at http://10.0.8.86:5240/MAAS/combo/angular.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):9:4093
    at completeOutstandingRequest (http://10.0.8.86:5240/MAAS/combo/angular.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):3:30368)
    at http://10.0.8.86:5240/MAAS/combo/angular.js?v=2.5.1(:5240/MAAS/7489-g2f2…c0-0ubuntu1~18.04.1):4:1206

Tags: ui

Related branches

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)
Steve Rydz (steverydz)
Changed in maas:
status: Triaged → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote :

Turned out that the problem was in the websocket handler, and not the JS code.

Changed in maas:
assignee: Steve Rydz (steverydz) → Björn Tillenius (bjornt)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.