Skip to:

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

Surveillance category membership of deleted nodes "leaks" in filters to interfaces of successor nodes

Description

Steps to reproduce:

1. Add a node via newSuspect with Capsd. Call that node's node-ID "N_o" (for Node-old)
2. Add node N_o to surveillance category Servers
3. Delete node N_o via the web UI
4. Repeat step 1 with the same IP address carried in the previous newSuspect. Call the new node's node-ID "N_n". DO NOT add N_n to any surveillance categories.
5. Create a filter rule either as part of a poller package or (for expediency) in the Notification Wizard that includes the term "catincServers"

Expected result: Node N_n does not pass the filter
Actual result: Node N_n does pass the filter
Further notes: Deleting node N_o entirely from the database should cause this behavior to abate.

This issue corresponds to MyNMS ticket #601.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alejandro Galue May 29, 2018 at 3:37 PM

Capsd doesn't exist on newer versions, and considering that now Provisiond handles discovered nodes, and the category membership rules have been changed, I'm pretty confident saying that this problem cannot be reproduced on newer versions. In fact, I've repeated the steps to reproduce the problem on a VM running latest Meridian 2017, and the filter behaves correctly (no matches).

Jeff Gehlbach August 17, 2011 at 10:16 AM

Assigning to self since I do like to fix the occasional bug

Cannot Reproduce

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created August 16, 2011 at 12:36 PM
Updated May 29, 2018 at 3:37 PM
Resolved May 29, 2018 at 3:37 PM