Flexible Schedule Downtime Fails to Clear

[GreatWolfResorts]

Looks like it's related to the start and end time, regardless of whether fixed or flexible is defined. I applied a flexible schedule downtime for 0 hours 15 minutes, but I made it a point to modify the end time to roughly 15 minutes as well in duration. The downtime initiated when the host was unavailable, as it should. It cleared the downtime when the specified "end time" was met. The second test I did was another flexible 0 hours 15 minutes:

Acknowledgements and comments for the host displaying:

This host has been scheduled for flexible downtime starting between 07-24-2012 10:44:48 and 07-24-2012 12:44:48 and lasting for a period of 0 hours and 15 minutes. Notifications for the host will not be sent out during that time period.

However, here you'll notice I didn't change the default end time of 2 hours. Sure enough, the host goes into downtime when it reaches a hard failure check. However, instead of clearing after the 15 minutes specified duration, it remains in downtime, 30 minutes later. I have a feeling that the duration is not even being considered when the flexible option is specified. Here is another round of event logs:

Code: Select all

2012-07-24 11:03:01HOST ALERT: GWR-SPWFE-IMM;UP;HARD;1;OK - : rta 0.813ms, lost 0%
2012-07-24 11:01:18HOST ALERT: GWR-SPWFE-IMM;DOWN;HARD;5;CRITICAL - : rta nan, lost 100%
2012-07-24 11:00:59HOST ALERT: GWR-SPWFE-IMM;DOWN;SOFT;4;CRITICAL - : rta nan, lost 100%
2012-07-24 11:00:41HOST ALERT: GWR-SPWFE-IMM;DOWN;SOFT;3;CRITICAL - : rta nan, lost 100%
2012-07-24 10:59:56HOST ALERT: GWR-SPWFE-IMM;DOWN;SOFT;2;CRITICAL - : rta nan, lost 100%
2012-07-24 10:59:29HOST DOWNTIME ALERT: GWR-SPWFE-IMM;STARTED; Host has entered a period of scheduled downtime

Host Details:

Code: Select all

Host State:	Up
Duration:	31m 13s
Host Stability:	Unchanging (stable)
Last Check:	07/24/2012 11:33:11
Next Check:	07/24/2012 11:38:14
Host Notes:	
Host is in scheduled downtime

[scottwilkerson]

We have been able to reproduce this behavior and have found it to be a bug in Nagios Core. We have submitted a bug report. You can feel free to see our findings at
http://tracker.nagios.org/view.php?id=359