[dev.icinga.com #12540] ScheduledDowntime always use next day

[icinga-migration]

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

Created by GreenRover on 2016-08-25 06:01:56 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-10-04 10:34:30 +00:00 (in Redmine)

Icinga Version: r2.4.10-1
Backport?: Not yet backported
Include in Changelog: 1

---

NOW is: 25.08.2016 07:19:03

I add this Rule to config.

apply ScheduledDowntime "4 - 11 - service" to Service {
    author = "icingaadmin"
    comment = "#4 HH wartung"
    ranges = {
        "2016-08-24" = "00:00-24:00"
        "2016-08-25" = "00:00-24:00"
        "2016-08-26" = "00:00-24:00"
        "2016-08-27" = "00:00-24:00"
        "2016-08-28" = "00:00-24:00"
        "2016-08-29" = "00:00-24:00"
        "2016-08-30" = "00:00-24:00"
        "2016-08-31" = "00:00-07:00"
    }
    fixed = true
    assign where service.host_name == "PC-HH"
}

Bud the spool "/v1/objects/downtimes" shows:

start_time: 1472162400,        // 26.08.2016 00:00:00
end_time: 1472248800,          // 27.08.2016 00:00:00
entry_time: 1472102343.063089, // 25.08.2016 07:19:03

The issue is based in the usage of wrong time range:

the system use:

"2016-08-26" = "00:00-24:00"

but should also add for today.

"2016-08-25" = "00:00-24:00"

Otherwise the critical services will only acknowledged at next day.

German description:
https://monitoring-portal.org/index.php?thread/37186-host-down-time-best%C3%A4tigt-services-nicht/&postID=235024#post235027

[icinga-migration]

Updated by GreenRover on 2016-08-30 05:39:18 +00:00

Please Reject
Is already fixed in: r2.5.3-1

[icinga-migration]

Updated by nlm on 2016-10-03 15:16:09 +00:00

GreenRover wrote:

Please Reject
Is already fixed in: r2.5.3-1

Please don't, i still get this problem in r2.5.4-1

I'm using these ranges :

  ranges = {
    monday = "00:00-24:00"
    tuesday = "00:00-24:00"
    wednesday = "00:00-24:00"
    thursday = "00:00-24:00"
    friday = "00:00-24:00"
    saturday = "00:00-24:00"
    sunday = "00:00-24:00"
  }

and the downtimes are programmed for the next day

Schedule downtime   created at 13:12 ǀ scheduled on Oct 4 02:00

(the 2 hours difference between the schedule and the display is because machine is in UTC tz and interface is UTC+2)

[Crunsher]

Closing as duplicate of #4790