Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
1.8.16, 1.12.9, 20.0.0, Meridian-2015.1.5, Meridian-2016.1.5
-
Security Level: Default (Default Security Scheme)
-
None
-
Horizon - June 21st, Horizon - June 28th
Description
When a node is deleted, collectd does not seem to unschedule that node from collection. This is a problem for a number of reasons, but mainly because datacollectionfailed events will still be generated even though the node, from the perspective of OpenNMS, does not exist.
Test case:
CentOS 6, OpenNMS 1.8.16, clean install
Add a node with SNMP
Verify that SNMP data collection is occurring.
Delete the node through the webUI.
A collection attempt will be made five minutes after the previous one and after the node has been deleted.
Delete the node from the database via psql.
A collection attempt will be made five minutes after the previous one and after the node has been deleted.
Attachments
Issue Links
- duplicates
-
-
- Closed
-