[checkmk-commits] [tribe29/checkmk] 474ab9: 14625 FIX fortigate_sync_status: No longer crashes...

Branch: refs/heads/2.1.0 Home: https://github.com/tribe29/checkmk Commit: 474ab9158d774dcc0d4bea882708bafb83a267bd https://github.com/tribe29/checkmk/commit/474ab9158d774dcc0d4bea882708bafb8… Author: LukaRacic <luka.racic(a)tribe29.com> Date: 2022-10-13 (Thu, 13 Oct 2022) Changed paths: A .werks/14625 M checks/fortigate_sync_status Log Message: ----------- 14625 FIX fortigate_sync_status: No longer crashes if the status is not available or is not known The check used to crash if the status of a cluster was not available (i.e. empty string) or if the status was not known (wasn't either 'synchronized' nor 'unsynchronized'). Now, if any of the above cases occur, the check turns to an UNKNOWN state and provides the appropriate description. Change-Id: If9451397b34b363c90bafb5fc4e02fdab3309232 Commit: a649e367bb20d5ba06f499fff673180652afc821 https://github.com/tribe29/checkmk/commit/a649e367bb20d5ba06f499fff67318065… Author: LukaRacic <luka.racic(a)tribe29.com> Date: 2022-10-13 (Thu, 13 Oct 2022) Changed paths: A .werks/14434 M cmk/base/plugins/agent_based/chrony.py M tests/unit/cmk/base/plugins/agent_based/test_chrony.py Log Message: ----------- 14434 FIX chrony check no longer crashes if chrony section is not available Change-Id: I2519129ba0d80c054a414219f61a022fc89bfc0a Compare: https://github.com/tribe29/checkmk/compare/ed2f9f938686...a649e367bb20