[checkmk-commits] [tribe29/checkmk] f268e1: 11352 FIX iptables: Keep ACK after update/restart

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: f268e12c649ceef47d597ca6bb2cdf0265d9007c https://github.com/tribe29/checkmk/commit/f268e12c649ceef47d597ca6bb2cdf026… Author: Timotheus Bachinger &lt;timotheus.bachinger(a)tribe29.com&gt; Date: 2021-02-04 (Thu, 04 Feb 2021) Changed paths: A .werks/11352 M checks/iptables Log Message: ----------- 11352 FIX iptables: Keep ACK after update/restart 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. Change-Id: If79680696ea85c36d894d9b5babba09e41312a8c