[OpenNMS/opennms] bbc2aa: NMS-20101: Only skip ticket creation while the ala...

  Branch: refs/heads/mm/NMS-20101-smoke
  Home:   https://github.com/OpenNMS/opennms
  Commit: bbc2aaf3bbaa2a225ce2337c3880469dc7ff3aed
      https://github.com/OpenNMS/opennms/commit/bbc2aaf3bbaa2a225ce2337c3880469dc7ff3aed
  Author: Marshall Massengill <[email protected]>
  Date:   2026-07-30 (Thu, 30 Jul 2026)

  Changed paths:
    M docs/modules/operation/pages/deep-dive/notifications/strategies/ticket.adoc
    M features/notifications/ticket-strategy/src/main/java/org/opennms/netmgt/notifd/TicketNotificationStrategy.java
    M features/notifications/ticket-strategy/src/test/java/org/opennms/netmgt/notifd/TicketNotificationStrategyTest.java

  Log Message:
  -----------
  NMS-20101: Only skip ticket creation while the alarm's ticket is active

Tickets that are closed, resolved, or cancelled, or whose creation
failed, no longer block a new ticket, so a re-fired problem can open a
fresh one.  Unknown state values stay on the blocking side, which also
covers a NULL tticketstate reading as 0 (OPEN) through JDBC getInt().
The comparison uses TroubleTicketState.getValue(), which matches the
ordinal the database stores for every current constant.

Allowing a retry after CREATE_FAILED goes beyond the alarmd drools
rules, which only create when the state is null; for a
notification-driven path a failed create should not permanently block
the channel.

Also returns a clean error instead of an NPE when the event row no
longer exists, and adds a point-of-use docs note recommending
single-user targets.



To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications


_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs