Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

collectd does not unschedule deleted nodes

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.

Acceptance / Success Criteria

None

duplicates

Lucidchart Diagrams

Activity

Show:

Jesse White June 26, 2017 at 4:06 PM

Jesse White June 23, 2017 at 3:09 PM

I've confirmed this is still an issue in the 1.12, foundation and foundation-2017 branches.

Benjamin Reed May 2, 2012 at 3:20 PM

I believe this was fixed as part of my changes for .

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created December 15, 2011 at 4:12 PM
Updated July 25, 2017 at 10:14 PM
Resolved June 28, 2017 at 3:26 PM