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 #11688] Outdated downtime/comments not removed from IDO database (restart) #4171
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11688
Created by mhein on 2016-04-27 10:31:11 +00:00
Icinga Web 2 tries to remove downtime 459, native interface tries to remove downtime 468. The native interface wins because this is the real downtime. If you try to delete the downtime in Icinga Web 2, nothing happens.
2016-06-03 12:40:37 +00:00 by mfriedrich 0ce4139
Updated by mfriedrich on 2016-05-02 13:35:26 +00:00
I've been investigating on that issue since Friday, I've opened an issue for referencing the fixed commit - #11711. Though I'm not sure if this is the same issue over here but maybe a side-effect.
Updated by Anonymous on 2016-05-31 04:43:15 +00:00
When creating a scheduled downtime via object and not via apply rule, this object is newly-created everytime, when Icinga2 restarts. It follows, that you have one downtime multiple times in Icingaweb, in the DB and in /var/lib/icinga2/api/packages/_api/XXX-1459918973-1/conf.d/downtimes/
Updated by mfriedrich on 2016-06-03 12:30:51 +00:00
Hm I think I found a way to reproduce this issue while looking into #11890:
Now the comment/downtime object has no host reference anymore, the config file will be deleted.
Comment/downtime still visible in
Sending in a manual delete has no effect (Icinga 2 doesn't know about the comment/downtime id, and does nothing)
So there is no guarantee with inserting a new host/service object into the database and purging old comments/downtimes.
AddComments() and AddDowntimes() will return silently if there are no comments/downtimes found in core memory. Although they will never be purged from the database then.
I'm currently testing a fix.