ID: 11352
Title: iptables: Keep ACK after update/restart
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In case a changed iptable config - which results in {CRIT} - was acknowledged, the ACK
vanished after a <tt>omd update<\tt> or <tt>omd restart<\tt>.
The reason therfore is that the check will go to state {OK} for one checkinterval after
the update/restart and then become {CRIT} again.
The intermediate state is now {PENDING}, which is actually more precise.