log1-c
commented
6 months ago Tested this on a different system and can confirm, but also with IcingaDB installed.
apply ScheduledDowntime "test123" to Host {
author = "Test"
comment = "test 123"
fixed = false
duration = 60m
ranges = {
"sunday 3" = "20:00-22:00"
}
assign where host.name == "g-ici-mon01"
}Object 'g-ici-mon01!test123' of type 'ScheduledDowntime':
% declared in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* __name = "g-ici-mon01!test123"
* author = "Test"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 2:4-2:18
* child_options = "DowntimeNoChildren"
* comment = "test 123"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 3:4-3:23
* duration = 3600
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 6:4-6:17
* fixed = false
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 5:4-5:16
* host_name = "g-ici-mon01"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* name = "test123"
* package = "_etc"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* ranges
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 8:4-10:4
* sunday 3 = "20:00-22:00"
* service_name = ""
* source_location
* first_column = 0
* first_line = 1
* last_column = 40
* last_line = 1
* path = "/etc/icinga2/zones.d/master/downtime.conf"
* templates = [ "test123" ]
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* type = "ScheduledDowntime"
* vars = null
* zone = "master"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40[2024-04-18 09:21:31 +0200] information/ConfigObjectUtility: Created and activated object 'g-ici-mon01!8ee97360-f554-4896-bf93-2a188859ad42' of type 'Downtime'.
[2024-04-18 09:21:31 +0200] information/Downtime: Added downtime 'g-ici-mon01!8ee97360-f554-4896-bf93-2a188859ad42' between '2024-04-21 20:00:00' and '2024-04-21 22:00:00', author: 'Test', flexible with 3600s duration
Change downtime to
apply ScheduledDowntime "test123" to Host {
author = "Test"
comment = "test 123"
fixed = false
duration = 60m
ranges = {
"sunday 4" = "20:00-22:00"
}
assign where host.vars.is_icinga2_master
}systemctl reload icinga2
Object 'g-ici-mon01!test123' of type 'ScheduledDowntime':
% declared in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* __name = "g-ici-mon01!test123"
* author = "Test"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 2:4-2:18
* child_options = "DowntimeNoChildren"
* comment = "test 123"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 3:4-3:23
* duration = 3600
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 6:4-6:17
* fixed = false
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 5:4-5:16
* host_name = "g-ici-mon01"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* name = "test123"
* package = "_etc"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* ranges
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 8:4-10:4
* sunday 4 = "20:00-22:00"
* service_name = ""
* source_location
* first_column = 0
* first_line = 1
* last_column = 40
* last_line = 1
* path = "/etc/icinga2/zones.d/master/downtime.conf"
* templates = [ "test123" ]
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40
* type = "ScheduledDowntime"
* vars = null
* zone = "master"
% = modified in '/etc/icinga2/zones.d/master/downtime.conf', lines 1:0-1:40[2024-04-18 09:26:55 +0200] information/Downtime: Added downtime 'g-ici-mon01.!498f381c-7246-42a9-815d-8d6a100f79d7' between '2024-04-28 20:00:00' and '2024-04-28 22:00:00', author: 'Test', flexible with 3600s duration
[2024-04-18 09:26:55 +0200] critical/ScheduledDowntime: Exception occurred during removal of obsolete downtime for scheduled downtime 'g-ici-mon01!test123': Error: Cannot remove downtime 'g-ici-mon01!8ee97360-f554-4896-bf93-2a188859ad42'. It is owned by scheduled downtime object 'g-ici-mon01!test123'Removing the config file then yields no results via icinga2 object list but both downtimes remain visible in the webinterface.
And no log entries any more like the one above.
Icinga2 2.14.2
Icinga Web 2 Version 2.12.1
icinga/icinga-php-library 0.13.1
icinga/icinga-php-thirdparty 0.12.1
director 1.11.1
icingadb 1.1.1
incubator 0.22.0
edit: Can only get rid of the downtimes in the webinterface when delteing, reloading and then recreating the host object
Mordecaine
Nayakum
yhabteab
Describe the bug
If I create a Scheduled Downtime in a global Zone via DSL, it is not possible to delete/change it afterwards
To Reproduce
Create a scheduled Downtime /etc/icinga2/zones.d/global-satellites/downtimes.conf:
icinga2 object list --type ScheduledDowntime --name 'msd-lwtest01!test123'Change Downtime:
icinga2 object list --type ScheduledDowntime --name 'msd-lwtest01!test123'Result: The old Downtime will not be changed and is still active In the Log you can find the following lines:
Expected behavior
The Downtime should be updated or deleted. Furthermore, in the logfile is written,
'Checkable msd-lwtest01!cpu' already in a NOT-OK state. Triggering downtime now, but the downtime should be started in the future and not at the reload time.Your Environment
Include as many relevant details about the environment you experienced the problem in
icinga2 --version): 2.14.1icinga2 feature list): api checker debuglog icingadb influxdb2 mainlog notification syslogicinga2 daemon -C): No Errorszones.conffile (oricinga2 object list --type Endpointandicinga2 object list --type Zone) from all affected nodes.