Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10843] DB IDO: downtime is not in effect after restart #3780
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10843
Created by mhein on 2015-12-15 10:46:29 +00:00
Icinga Web 2 shows downtimes with time periods in the past as not running. The classic interface shows 'in effect'.
2016-03-23 12:42:00 +00:00 by mfriedrich 98e1d70
2016-04-20 08:07:22 +00:00 by mfriedrich 1b69a7f
Updated by jflach on 2016-01-04 10:43:56 +00:00
I could reproduce this.
Created a downtime
It also shows up as not-in-effect in icingaweb2. I will investigate this a bit further but currently I have no idea how or why this happens.
Updated by mfriedrich on 2016-02-04 13:40:09 +00:00
I'm unable to reproduce this issue with the current git master.
Updated by mfriedrich on 2016-02-04 13:43:57 +00:00
Probably this issue exists in 2.3.x but has been fixed either in 2.4.0 or with the latest changes applied for the next version. I'm therefore closing this issue.
Updated by mfriedrich on 2016-03-23 12:41:44 +00:00
I think I found a similar behaviour today. When the downtime is added once, and then triggered, everything is fine. Once you restart the core the downtime is not necessarily triggered again. The condition for checking 'is_in_effect' was different in statusdatawriter and ido*connection. Furthermore such "loaded" downtimes do not update the scheduled_downtime_depth similar to what TriggerDowntime does.