Skip to content

NMS-20105: Close the trouble ticket when the alarm clears - #8720

Open
cgorantla wants to merge 2 commits into
foundation-2024from
cg/jira/NMS-20105
Open

NMS-20105: Close the trouble ticket when the alarm clears#8720
cgorantla wants to merge 2 commits into
foundation-2024from
cg/jira/NMS-20105

Conversation

@cgorantla

Copy link
Copy Markdown
Contributor

The notification command now sends a close for a cleared alarm that still has an active ticket, instead of creating another one, so the resolution delivery completes the workflow. Renames the example command to troubleTicket.

External References

The notification command now sends a close for a cleared alarm that still has an
active ticket, instead of creating another one, so the resolution delivery
completes the workflow. Renames the example command to troubleTicket.
@github-actions github-actions Bot added the docs label Jul 31, 2026
@github-actions
github-actions Bot requested a review from indigo423 July 31, 2026 20:15
@cgorantla
cgorantla changed the base branch from develop to foundation-2024 July 31, 2026 20:15
@marshallmassengill
marshallmassengill self-requested a review August 3, 2026 12:23

@marshallmassengill marshallmassengill left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Close races alarmd, fails silently. sendResolvedNotificationsToUser queues at now. initial-delay applies only to the original notice. If notifd's SELECT a.severity beats alarmd's clear commit, isCleared() is false, control falls to the create branch, hasActiveTicket() returns 0, and nothing happens. answeredby LIKE '%auto-acknowledged%' is written synchronously before the re-run (NotificationManager.java:713-729).
  • Manually acked notice never closes its ticket (not sure this matters but putting the observation in here)
  • CLOSE_PENDING isn't in INACTIVE_TICKET_STATES, so an in-flight UI close gets a duplicate close; ditto every escalation stage / group member. Create side has a guard but close side doesn't.
  • isTicketCreationPending can't fire for this strategy's own creates. createTicketForAlarm sets only OPEN/CREATE_FAILED
  • Tests leave m_severity == 0, not a valid OnmsSeverity id

@marshallmassengill marshallmassengill left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants