ipdevpoll statuscheck errors out on some Aruba switches
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Medium
|
Morten Brekkevold |
Bug Description
We are getting repeated errors from the ipdevpoll statuscheck job concerning a customer's Aruba switches:
2016-06-14 08:44:34,135 [ERROR jobs.jobhandler] [statuscheck aruba-sw.
Traceback (most recent call last):
File "/usr/lib/
manager.save()
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
self.
File "/usr/lib/
to_purge = self.get_
File "/usr/lib/
self.
File "/usr/lib/
in dfs_tree
T.add_
File "/usr/lib/
for e in ebunch:
File "/usr/lib/
in dfs_edges
stack = [(start,
File "/usr/lib/
return self.adj[n]
KeyError: <NetboxEntity: Chassis (Unnamed entity) at aruba-sw>
It seems this problem arises because the Aruba switches do not present with any chassis entities in ENTITY-
This has unintended consequences for the system plugin, which, since it cannot see that any chassis devices have been found, creates a new one to store a collected software version in. The system plugin does not run during a statuscheck job, however, so the algorithm that checks for missing devices fails.
Changed in nav: | |
status: | Fix Committed → Fix Released |
Although it isn't really clear to me what to do with devices that claim to have no chassis at all, it seems we need to fix this problem in two ways:
First, the 'missing devices' algorithm should handle the case where a missing device is unknown to any plugins - but this will result in deleting it during a statuscheck.
Second, the system plugin should probably never create the chassis device in the first place, if it sees that the device has no chassis but at least one root entity.