A device is sometimes shown on the Node Listing Page

[Andres Rodriguez]

A device is sometimes shown on the MAAS Node Listing Page. This comes and goes, and seems to be a JS error.

[Blake Rouse (blake-rouse)]

I think this is related to a misbehaving trigger. The triggers need to check if its a device or a node and send the correct notification.

[Ricardo Bánffy (rbanffy)]

Does it follow any discernible pattern? Where is this MAAS running and what were the devices misreported as nodes?

[Blake Rouse (blake-rouse)]

As the bug states it was in the nodes listing page. A device will show up if you refresh it will go away and it might show up later, that is why I believe it is a trigger problem. Please take a look at the trigger to see if you can fix the problem.

[Ricardo Bánffy (rbanffy)]

I checked the trigger functions themselves and they seem mostly OK - the only code that could possibly fire a node_update event for a device involves changing storage configuration of a node (which, if it's happening, would be a separate bug). Another hypothesis would be that those specific triggers are firing for the devices when they shouldn't, either by being misattached to the wrong events or by cascading update events. That's why we need to know what exactly happened and when, because something caused the device to show up on the wrong pipe.

[Ryan Collis (vyan)]

In my case I simply added my new devices (brocade switch x3) all 3 showed as nodes the next time I loaded the nodes page. The only way I found to clear it up was deleting both the problem "nodes" and the matching device. If I delete the node only, the devices will all show as nodes within 5 min.

[Ricardo Bánffy (rbanffy)]

Thanks, Ryan. Can you do a "dpkg -l '*maas*' | cat" so we know the exact version of MAAS you are running and get the contents of "/var/log/maas/*"?

[Ryan Collis (vyan)]

Richardo: DPKG info is below. I will post the logs first thing tomorrow morning as I am writing this from my mobile.
dpkg -l '*maas*' | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============================-===================================-============-======================================
ii maas 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS command line API tool
ii maas-cluster-controller 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS server cluster controller
ii maas-common 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS server common files
ii maas-dhcp 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS DHCP server
ii maas-dns 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS DNS server
ii maas-proxy 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS Caching Proxy
ii maas-region-controller 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS Server minimum region controller
ii python-django-maas 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS server Django web framework
ii python-maas-client 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS python API client
ii python-maas-provisioningserver 1.9.0~alpha3+bzr4363-0ubuntu1~wily1 all MAAS server provisioning libraries

[Ricardo Bánffy (rbanffy)]

Thank you, Ryan. What were the configurations of the switches you added - name, ip assignment, networks/addresses if any? How did you get from the devices page to the nodes page - was it from the "n Nodes | m Devices" next to the MAAS server name or the "Nodes" link on the top bar? What browser are you using (may be relevant if it's a JavaScript issue)?

[Mark Shuttleworth (sabdfl)]

I see this occasionally with Chrome on Ubuntu - it looks very much like
a JS issue.

Mark

[Ryan Collis (vyan)]

I am using Safari and chrome on Mac OS X 10. I generally use the nodes link from the menu at the top. The switches were named with our convention which would be switchidZONENAME.domain and ip was static within the same net as the cluster/region 10.×.×.× and one switch in our management net 172.×.×.× set as external. I can also confirm the issue using the nodes | devices link.

[Ryan Collis (vyan)]

I should add that this is on our standalone development cluster. Version 1.9.0 (alpha4+bzr4371)

[Andres Rodriguez (andreserl)]

Hi Ryan,

Is there anything special you are doing with this MAAS? Are the devices (switches) DHCP'ing from MAAS or is there any commissioning happening?

Thanks

[Andres Rodriguez (andreserl)]

Ok, we have identified the issue. This seems like a few triggers were incorrectly updating the nodes in the list making the device to show up as a node. This will be fixed in the next release.

[Ricardo Bánffy (rbanffy)]

In order to reproduce the issue, have the nodes list open in one window and issue a command line call that changes storage parameters on the device's node_id, such as (example extracted from Andres' comment on the merge request that fixed the issue).

maas <login> node set-storage-layout <node-uuid> storage_layout=lvm

On an affected release, this will make the device show up on the nodes list.