Issues
- Alarm not cleared after Path Outage Node came back UPNMS-17720
- OpenNMS failed to forward alarms on configured kafka topic with a filter condition.NMS-16454
- Horizon 33.0.2-1 on CentOS9 - Alarm/Event list paging filters issueNMS-16421Resolved issue: NMS-16421Christian Pape
- Unable to query REST alarms for null ackUserNMS-16285
- DroolsAlarmContext error - alarm facts out of syncNMS-16208Chandra Gorantla
- OpenNMS alarms pushed to Elasticsearch may have incorrect mappingNMS-15815
- Alarm Sounds and acknowledgement also for the Dashboard.NMS-15452Resolved issue: NMS-15452
- No way to know the alarm type (as type 1, 2 or 3) from web UINMS-14578Resolved issue: NMS-14578Christian Pape
- Alarms "Long Listing" resets the advanced searchNMS-14481Resolved issue: NMS-14481
- Enhance Alarm schema to track state transitionNMS-14466
- Snmp Link Up does not clear Snmp Link DownNMS-14378Resolved issue: NMS-14378Benjamin Reed
- Grafana Panel Internal Server Error when lasteventid is Null for an Alarm when Using HELMNMS-14331Resolved issue: NMS-14331Alberto
- Kafka-Producer Alarm Resync Failing Post Entire Kafka Cluster OutageNMS-14321Resolved issue: NMS-14321Alex May
- Alarms Advanced Search Not WorkingNMS-14313Resolved issue: NMS-14313Pushkar Suthar
- Inconsistent content of forwarded Kafka alarm (clear_key in particular)NMS-13699Resolved issue: NMS-13699
- The %dpname% breaks the alarm life-cycle when having multiple minions per locationNMS-13210Resolved issue: NMS-13210Christian Pape
- When using a custom prefix, the Elasticsearch Forwarder for events and situation-feedback creates a wrong template.NMS-13030Resolved issue: NMS-13030Chandra Gorantla
- When using a custom prefix, the Elasticsearch Forwarder for events and situation-feedback creates a wrong template.NMS-13017Resolved issue: NMS-13017Chandra Gorantla
- Clearing an alarm brings alarm not found messageNMS-12981Resolved issue: NMS-12981Thomas Bigger
- Integration API: Alarm.type is unsetNMS-12923Resolved issue: NMS-12923Mike Kelly
- NPE while running AlarmLifecycleListenerManagerNMS-12825Resolved issue: NMS-12825Chandra Gorantla
- Searching for alarms in the v2 API with a reductionKey that includes a comma or semicolon results in a 500 errorNMS-12777Resolved issue: NMS-12777David Schlenk
- Be able to ignore certificate validation on all Karaf features that push data to ElasticsearchNMS-12768Resolved issue: NMS-12768Chandra Gorantla
- inadequate performance of alarms endpoint of v1 REST APINMS-12764
- Eventconf with same UEI but differing masks does not follow first-found-wins rule when some events have alarm-data elements and some do notNMS-12755Resolved issue: NMS-12755Jesse White
- The Alarm History feature is not workingNMS-12718Resolved issue: NMS-12718Chandra Gorantla
- Improve alarmd Drools engine performance by using STREAM modeNMS-12455Resolved issue: NMS-12455Jesse White
- Alarmd fails intermittently and OOMsNMS-12412Resolved issue: NMS-12412Jesse White
- "Page Not Found" in alarm-list when choosing number of alarms in dropdown-listNMS-12379Resolved issue: NMS-12379Markus von Rüden
- Memory leak in Drools engine for alarmdNMS-12322Resolved issue: NMS-12322Jesse White
- A user with ROLE_READONLY can make modifications to Alarms and notifications.NMS-12204Resolved issue: NMS-12204
- Configurable index name for Event & Alarm ForwarderNMS-12082Resolved issue: NMS-12082Jesse White
- Show managed object type and instance on alarm details pageNMS-11666Resolved issue: NMS-11666Chandra Gorantla
- Cannot clear alarmsNMS-11129Resolved issue: NMS-11129
- Increment Severity of SituationsNMS-10886Resolved issue: NMS-10886David Smith
- Journal Memo doesn't work if reductionkey bigger than 256 charactersNMS-10438
36 of 36
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 9 hours 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