Every day at 11:08 the cli check fails and recovers at 11:13

[slalomsk8er]

Describe the bug

The check runs '/usr/bin/icingacli' 'x509' 'check' 'host' '--critical' '3d' '--host' 'ictlogbwp01.example.com' '--ip' '10.5.72.147' '--port' '443' '--warning' '7d' and at 11:08 results in a Critical with a non helpful message CRITICAL - ictlogbwp01.uhbs.ch: ; ictlogbwp01..example.com expires in 101 days and at 11:13 it recovers with OK - ictlogbwp01.uhbs.ch expires in 101 days .

To Reproduce

Have jobs scanning a big VLAN and have Services with '/usr/bin/icingacli' 'x509' 'check's attached to hosts in the VLANs.

Expected behavior

Results are stable and don't produce intermittent problem states only to recover again without clear reason.
Messages are a clear indicator, why the module thinks the host ip port triplet is in problem state.

• Icinga Web 2 version and modules (System - About):
  

• Web browser used: Chrome 130.0.6723.58

• Icinga 2 version used (icinga2 --version): r2.14.2-1

• PHP version used (php --version): 8.1

• Server operating system and version: Debian 12

[slalomsk8er]

From a mailbox overview I got from one of my customers, it looks like I need to consolidate all the downtimes I created per job into one and add all schedules from every job and apply to all checks using /usr/bin/icingacli' 'x509' 'check' ... to suppress this false positives.