[2.0rc2] maasserver.websockets.base.HandlerNoSuchMethodError: node_actions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I upgraded to MAAS RC2 from MAAS B3, and started seeing this after I selected to commission all my nodes. Basically, I upgraded, re-enlisted nodes, and commissioning them all (43). The result was:
2016-07-15 02:14:25 [HTTPChannel,
Traceback (most recent call last):
File "/usr/lib/
return callWithContext
File "/usr/lib/
return context.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
--- <exception caught here> ---
File "/usr/lib/
why = selectable.doRead()
File "/usr/lib/
return self._dataRecei
File "/usr/lib/
rval = self.protocol.
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
if self.handleRequ
File "/usr/lib/
d = handler.
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
raise HandlerNoSuchMe
Changed in maas: | |
status: | Incomplete → Invalid |
This apparently is a UI only issue where after the upgrade, the UI code tries to acccess node_actions, wchih is no longer there. a F5 or the UI auto released should fix this, but may not happen immediately.