Uploaded image for project: 'OpenNMS Horizon'
  1. OpenNMS Horizon
  2. HZN-1503

Related alarms are not deleted from situations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 24.0.0
    • Fix Version/s: 24.0.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Horizon - March 20th 2019

      Description

      It possible to trigger alarms and create a new situation using:

      ./bin/send-event.pl uei.opennms.org/alarms/trigger \
        -p 'node n6' \
        -x 6
      ./bin/send-event.pl uei.opennms.org/alarms/trigger \
        -p 'node n7' \
        -x 7
      ./bin/send-event.pl uei.opennms.org/alarms/trigger \
        -p 'related-reductionKey1 uei.opennms.org/alarms/trigger:n7::' \
        -p 'related-reductionKey2 uei.opennms.org/alarms/trigger:n6::' \
        -p 'node situation-n6-n7'
      

      The related reduction keys on the event are supposed to be authoritative, meaning that if I subsequently send:

      ./bin/send-event.pl uei.opennms.org/alarms/trigger \
        -p 'related-reductionKey1 uei.opennms.org/alarms/trigger:n7::' \
        -p 'node situation-n6-n7'
      

      Then the alarm with reduction key 'uei.opennms.org/alarms/trigger:n6::' should be removed from the situation.

      This functionality is no longer working, and the alarm remains in the situation.

        Attachments

          Activity

            People

            • Assignee:
              j-white Jesse White
              Reporter:
              j-white Jesse White
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: