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

Branch: refs/heads/2.0.0 Home: https://github.com/tribe29/checkmk Commit: e6e4b54544818519bef1fc1baa2e69614074f3db https://github.com/tribe29/checkmk/commit/e6e4b54544818519bef1fc1baa2e69614… 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' or '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: 3efd943dec1316a5d984270ac97fa2a775325fcd https://github.com/tribe29/checkmk/commit/3efd943dec1316a5d984270ac97fa2a77… 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/63728df251ff...3efd943dec13