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

Ticket-creating automations are incorrectly enabled by default

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • 25.0.0, Meridian-2019.1.1
    • Meridian-2019.1.2, 25.1.2
    • Ticketing
    • Security Level: Default (Default Security Scheme)
    • None
    • Horizon 2019 - December 11th

    Description

      In translating the old SQL automations into the new Drools way of doing automations, we overlooked the fact that the createTickets, createCriticalTicket, updateTickets, closeClearedAlarmTickets, and clearAlarmsForClosedTickets automations were disabled by default. This means that on any system migrated from Meridian 2018 or earlier or from Horizon 24 or earlier, on which a ticketer plugin is configured and the ticketer is enabled, a ticket will be created for most every alarm. This is not typically the desired behavior.

      We can easily disable these automations by adding enabled false before the rule's when (left-hand) side. This change may result in rpmnew files on Meridian, but the risk of surprise ticket creation likely outweighs the pain of dealing with one rpmnew.

      Attachments

        Activity

          People

            cpape Christian Pape
            jeffg Jeff Gehlbach
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: