Won't Fix
Details
Assignee
UnassignedUnassignedReporter
Chris PhillipsChris PhillipsLabels
HB Grooming Date
Oct 27, 2021Components
Affects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Chris Phillips
Chris PhillipsLabels
HB Grooming Date
Oct 27, 2021
Components
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created April 17, 2005 at 12:48 PM
Updated November 1, 2021 at 7:54 PM
Resolved November 1, 2021 at 7:38 PM
When a node is discovered to have a new service, it is not recategorized
accordingly on the UI. In my own specific scenario, a cisco 801 router without
any SNMP access at all is replaced with an 837 WITH SNMP access. upon capsd
discovering the new SNMP capabilities, the nodeServiceGained event follows
through as expected and is fully updated. It does not however move from one
category for routers without SNMP to the group for routers WITH SNMP. Only by
restarting the opennms service am I able to make this node be correctly
categorized. Totally new nodes discovered by scheduled runs of discovery are
added directly to the correct groups also, so is solely an issue with nodes
gaining services.