-
Notifications
You must be signed in to change notification settings - Fork 571
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
Scheduled Downtime won't be changed/deleted after reload #10042
Comments
I think all scheduled downtimes are affected: |
Not entirely the same behaviour, but I had a similar issue a couple years back where downtimes were "copied" by changing aspects of them, e.g. adding comments: #9142 At that time, it was considered as working as intended. |
ref/IP/53497 |
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
icinga2 object list --type ScheduledDowntime --name 'msd-lwtest01!test123'
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.conf
file (oricinga2 object list --type Endpoint
andicinga2 object list --type Zone
) from all affected nodes.The text was updated successfully, but these errors were encountered: