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 #11336] Use retry_interval instead of check_interval for first OK -> NOT-OK state change #4014
Comments
Updated by mfriedrich on 2016-03-09 10:34:46 +00:00
|
Updated by mfriedrich on 2016-03-11 09:32:01 +00:00
|
Updated by mfriedrich on 2016-03-11 11:02:22 +00:00
Applied in changeset 7fb8bcd. |
Updated by mfriedrich on 2016-03-16 15:01:54 +00:00
|
Updated by mfriedrich on 2016-03-16 15:49:49 +00:00 Positive feedback here: https://dev.icinga.org/issues/11243#change-49461 I'd like to see more testers so we can safely backport this to 2.4.5+. |
Updated by mfriedrich on 2016-03-24 09:37:58 +00:00
|
Updated by mfriedrich on 2016-03-24 10:06:45 +00:00
|
Updated by gbeutner on 2016-04-20 08:15:57 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11336
Created by mfriedrich on 2016-03-09 10:34:33 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-03-11 11:02:22 +00:00)
Target Version: 2.4.5
Last Update: 2016-04-20 08:15:57 +00:00 (in Redmine)
The logic remains in ProcessCheckResult(). The previous fix for this problem in #7287 was broken and has been reverted.
Changesets
2016-03-11 11:00:30 +00:00 by mfriedrich 7fb8bcd
2016-03-15 12:02:38 +00:00 by mfriedrich d682f56
2016-03-15 13:02:19 +00:00 by mfriedrich a30cb86
2016-04-20 08:00:07 +00:00 by mfriedrich 122256b
2016-04-20 08:00:08 +00:00 by mfriedrich 8668eb6
2016-04-20 08:00:09 +00:00 by mfriedrich e076e91
Relations:
The text was updated successfully, but these errors were encountered: