No information collected for devices of unknown type

[Morten Brekkevold]

When a new IP device is added, whose type is unknown to NAV, ipdevpoll will stop all polling jobs and the device data remains uncollected.

It appears that as ipdevpoll discovers that the device's type has "changed", i.e. it was unknown before but now we have a new sysObjectID, it sends the netbox_type_changed signal and stops all jobs for the device. For some reason, the jobs are never rescheduled.

ipdevpoll shouldn't send the netbox_type_changed signal when the type was previously unknown, since that indicates the box has not been polled before.

This may also have ramifications for actual type changes, which should also be tested properly.

[Morten Brekkevold (mbrekkevold)]

this has been fixed on the 3.8.x branch, http://metanav.uninett.no/hg/series/3.8.x/rev/1785b29ef444 . There are no more scheduled releases on the 3.8 series, so this will likely be part of the next 3.9 release.