Werk #22475: ntp: report why a falseticking peer is critical
| Component | Checks & agents | ||||||
| Title | ntp: report why a falseticking peer is critical | ||||||
| Date | Sep 22, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
If the NTP client rejected one of its peers as a falseticker, the corresponding
NTP Peer service went UNKNOWN with
ValueError: 'summary' must be non-empty str or None and produced a crash report
instead of a result. The check yielded the CRIT result for that peer without any
text.
The service now reports State: falsetick as the reason for the CRIT, matching
how the other peer states are shown.