Branch: refs/heads/2.2.0
Home:
https://github.com/tribe29/checkmk
Commit: 0c48b0545284bd9cd9d59235f9dffaf3de17eeac
https://github.com/tribe29/checkmk/commit/0c48b0545284bd9cd9d59235f9dffaf3d…
Author: Teresa Siegmantel <teresa.siegmantel(a)tribe29.com>
Date: 2023-04-11 (Tue, 11 Apr 2023)
Changed paths:
M cmk/gui/plugins/openapi/restful_objects/response_schemas.py
Log Message:
-----------
rest-api: remove 'password' field from PasswordExtensions
CMK-12793
Change-Id: Ie7007b4efb8acd54b468a73add3f705bcea9bed7
(cherry picked from commit e7672bb353319c31d7e3d656c6a6f67c31195562)
Commit: a7188377e72f088cae2dd8ffc65a021cd26da7bf
https://github.com/tribe29/checkmk/commit/a7188377e72f088cae2dd8ffc65a021cd…
Author: Joerg Herbel <joerg.herbel(a)tribe29.com>
Date: 2023-04-11 (Tue, 11 Apr 2023)
Changed paths:
A .werks/15415
M cmk/gui/views/perfometer/legacy_perfometers/check_mk.py
Log Message:
-----------
15415 FIX Interface checks: Fix error in perfometer rendering
From 2.2 onwards, the interface services do not produce
useless and
potentially wrong all-zero metrics anymore (werk #14542). This had an
unwanted side effect: Until the counters are initialized, there was a
fallback to the legacy perfometer because the non-legacy one is missing
metrics. The legacy perfometer assumed that all metrics are present
(pre-2.2 behaviour), which led to a crash.
To solve this issue, we simply remove the legacy perfometer for
interface checks.
CMK-12785
Change-Id: I2f980823c7161ad70f18590abea99f18c729d829
Compare:
https://github.com/tribe29/checkmk/compare/c9cd54b168fc...a7188377e72f