-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #12670] Forced custom notification is setting "force_next_notification": true permanently #4646
Labels
Milestone
Comments
Updated by mfriedrich on 2016-11-16 09:18:41 +00:00
|
Updated by mfriedrich on 2016-11-17 10:46:12 +00:00
Nice catch, thanks.
|
Updated by mfriedrich on 2016-11-17 10:55:03 +00:00
Applied in changeset a13e6b3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12670
Created by matus on 2016-09-07 14:37:49 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-11-17 10:55:03 +00:00)
Target Version: 2.6.0
Last Update: 2016-11-17 10:55:03 +00:00 (in Redmine)
Hi,
Not sure if this is a bug or I'm doing something wrong.
All notifications were working as expected, they were sent according to configured time periods until I sent custom notification from web interface and check the "Forced" option.
Checking "Forced" option had set the "force_next_notification: true" and all other notifications for this service/host are always forced and ignoring the time periods. In order to clear the flag force_next_notification I had to delete /var/lib/icinga2/icinga2.state.
Is this behaviour expected? Is there any other way of clearing/setting the "force_next_notification"
I have tested it on: icinga 2.5.4-1
ppa1trusty2, icingaweb 2.3.4-3ppa1, and icinga 2.4.4-1ppa1trusty1, icingaweb 2.2.0-1ppa1. Same result.I can pass the configs, but I believe you should be able to replicate it without it.
Thanks
Matus
Changesets
2016-11-17 10:53:35 +00:00 by mfriedrich a13e6b3
2016-11-28 11:10:13 +00:00 by mfriedrich 8d47b55
The text was updated successfully, but these errors were encountered: