Issues
- Alarm not cleared after Path Outage Node came back UPNMS-17720
- Allow basic auth credentials / scv metadata in external requisition URLNMS-17318Jahanzeb Akhtar
- Log messages from Groovy are truncatedNMS-17070Resolved issue: NMS-17070Muhammad Junaid
- Enhancement: thresholds values from other metrics or strings.propertiesNMS-17069
- WS-Man kerberos authentication fails with Java 17 since OpenNMS 33.0.10NMS-17009
- Handle if CA cert with alias already exists for MinionNMS-17007
6 of 6
Alarm not cleared after Path Outage Node came back UP
Description
Environment
Linux 4.18.0-553.6.1.el8.x86_64 (amd64) - CentOS8
Acceptance / Success Criteria
None
Details
Assignee
UnassignedUnassignedReporter
CARUANA, BRANDONCARUANA, BRANDONHB Grooming Date
Mar 26, 2025HB Backlog Status
Refined BacklogComponents
Sprint
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
CARUANA, BRANDON
CARUANA, BRANDON
HB Grooming Date
Mar 26, 2025
HB Backlog Status
Refined Backlog
Components
Sprint
Fix versions
Affects versions
Priority
MediumPagerDuty
PagerDuty
PagerDuty
Created March 3, 2025 at 2:45 PM
Updated 4 days ago
Activity
Show:
In a Path Outage setup, if the parent node is down, alarm is generated for the parent node, and all child nodes. Notification is only sent for parent node. This is OK.
When the parent node is back up, resolved notification is sent for the parent node and the alarm for the parent node is cleared. This OK.
The alarms for the child nodes are not cleared and have to be cleared manually, even if they are UP. < Not OK
Refer to:
https://opennms.discourse.group/t/alarm-not-cleared-after-path-outage-node-came-back-up/1751