Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-9369

Business service states are not properly updated when alarms are deleted

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 18.0.0, 18.0.1, 18.0.2, 18.0.3, 18.0.4, 19.0.0, 19.0.1, 19.1.0
    • 20.0.0, Meridian-2017.1.0
    • BSM
    • Security Level: Default (Default Security Scheme)
    • None
    • Horizon - May 24th

    Description

      If a business service relies on an alarm with a given reduction key, and that alarm is triggered and then subsequently deleted, the business service will not update it's state accordingly until either A) OpenNMS is restarted or B) the alarm gets triggered again.

      This can occur during normal usage, since vacuumd deletes alarms with the garbageCollect and fullGarbageCollect automations, if the alarms have been "idle" for at least a week.

      Attachments

        Activity

          People

            j-white Jesse White
            j-white Jesse White
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.