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 #12401] Fixed downtime start does not update actual_start_time #4460
Comments
Updated by mfriedrich on 2016-08-11 09:46:11 +00:00
|
Updated by mfriedrich on 2016-08-11 10:07:48 +00:00
The underlying problem is that Icinga Web 2 checks whether actual_start_time is set, but not scheduled_start_time. The column is only update once a downtime is triggered, which is false for fixed downtimes (but true for flexible downtimes).
|
Updated by mfriedrich on 2016-08-11 10:09:48 +00:00
Setting the actual_start_time for fixed downtimes only fixed the core bug. It has been sitting there for quite a while now, so congrats for the finding :) Fixed output:
|
Updated by mfriedrich on 2016-08-11 10:15:05 +00:00
Applied in changeset 4109448. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12401
Created by bsheqa on 2016-08-11 08:36:28 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-08-11 10:15:05 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-11 10:15:05 +00:00 (in Redmine)
When I set a downtime, the DOWNTIME START event is not in the history. DOWNTIME END is displayed correctly.
Steps to reproduce:
Attachments
Changesets
2016-08-11 10:10:27 +00:00 by mfriedrich 4109448
The text was updated successfully, but these errors were encountered: