Skip to content
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 #12395] Flexible downtimes should be removed after trigger_time+duration #4458

Closed
icinga-migration opened this issue Aug 10, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Aug 10, 2016

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12395

Created by mfriedrich on 2016-08-10 14:05:31 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-08-10 15:20:05 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-10 15:20:05 +00:00 (in Redmine)

Icinga Version: 2.4.10
Backport?: Not yet backported
Include in Changelog: 1

Currently all downtimes are removed once end_time is reached. If trigger_time+duration < end_time then the downtime will not be deleted

Changesets

2016-08-10 15:15:27 +00:00 by mfriedrich 8389d01

Fix flexible downtimes expiry time and removal

fixes #12395
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 10, 2016

Updated by mfriedrich on 2016-08-10 15:13:58 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
  • Target Version set to 2.5.0
  • fixed: end_time < now
  • flexible:
    • triggered && !in_effect -> expired
    • !triggered && end_time < now -> expired

In addition, OnDowntimeRemoved must check the following before sending a notification:

  • flexible && !triggered -> don't send a downtime stop notification
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 10, 2016

Updated by mfriedrich on 2016-08-10 15:20:05 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 8389d01.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.