have just upgraded to Icinga 2.12.3/icinga web 2.8.2 from 2.11.x/2.6.x and it all went quite well except for ACKs. There were quite a few ACKs that had been in place for quite some time and they have fallen out of the ACK state - the object clearly states that they are ‘not ACK’d’ but when I go to ACK the service or host again I see:
icinga2: Can’t send external icinga command: …service … is already acknowledged.
Important to know: If I make an ACK on a new critical that appears for example, it’s OK.
In this thread: Acknowledgements not syncing between masters
I read of someone having the same issue. So I checked my Modules - monitoring - Backends entries and I have one Command Transport which is a Transport of Icinga2 Api nature. And that is the only entry, I have tested the credentials with an API call and it’s ok. I do not have my 2 masters as entries under ‘Transport’ and that thread says to have them both listed but I am not sure this is exactly the same issue.
TLDR: old ACK’s existing prior to Icinga upgrade to latest version are no longer ACK’d but Icinga will not re-ack them as they are considered as ACK’d despite now showing as so, with an error message appearing if attempting to ACK.
one edit: notifications are switched off via the global notifcations switch