Branch: refs/heads/2.0.0
Home:
https://github.com/tribe29/checkmk
Commit: 46156348139d2d0f60faa5266ad5cfa7f92e24a9
https://github.com/tribe29/checkmk/commit/46156348139d2d0f60faa5266ad5cfa7f…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2023-03-16 (Thu, 16 Mar 2023)
Changed paths:
M tests/unit/cmk/base/test_check_table.py
Log Message:
-----------
extend check table tests
Change-Id: Ia57cd257824e1d4f18f78ec2cb578f2fb49e7bca
Commit: 97ba674295264c951d8d8976bb1c2692cef3f21d
https://github.com/tribe29/checkmk/commit/97ba674295264c951d8d8976bb1c2692c…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2023-03-16 (Thu, 16 Mar 2023)
Changed paths:
A .werks/15247
M cmk/base/check_table.py
M tests/unit/cmk/base/test_check_table.py
Log Message:
-----------
15247 FIX Prefer enforced services over discovered ones if clustered
This werk only affects users that have cluster nodes with enforced services which are
clustered <b>and could be discovered</b> on the node as well.
This werk changes the preference of services that are both enforced and discovered if they
are clustered.
For non-clustered services, an enforced service will take precedence over a discovered
service (if they share the description).
Prior to this werk, the order of preference was reversed if the service was clustered.
This is now fixed:
An enforced service will always take precedence over a discovered one in case both are
present.
Note that the parameters of these two services might not be the same:
The enforced service will have parameters as specified in the corresponding rule.
The discovered services parameters are determined by the rules matching the host were it
will be shown.
This change makes the parameters of the clustered enforced service more reliable in the
sense that they no longer depend on whether a service by the same description is
discovered on the nodes.
Change-Id: I3c9fc397f5e6131d78d926be54701383fe5005ed
Compare:
https://github.com/tribe29/checkmk/compare/902423a9099a...97ba67429526