30 Mar
2021
30 Mar
'21
11:02 a.m.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 06a2a6a8b8463eae15e32cc6598878bfd80170c0
https://github.com/tribe29/checkmk/commit/06a2a6a8b8463eae15e32cc6598878bfd…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-03-30 (Tue, 30 Mar 2021)
Changed paths:
A .werks/12553
A cmk/gui/watolib/host_label_sync.py
M cmk/utils/labels.py
M tests/unit/cmk/gui/test_background_job.py
M tests/unit/cmk/gui/test_cron.py
M tests/unit/cmk/gui/watolib/test_watolib.py
M tests/unit/cmk/utils/test_labels.py
Log Message:
-----------
12553 FIX Agent bakery: Fix host label conditions in distributed setups
In previous Checkmk versions agent bakery rules that were using host label
conditions could not be used correctly in distributed setups.
The background is that in distributed setups the discovered(!) host labels are
stored on remote sites for hosts that are assigned with a remote site. But the
processing of agent bakery rules is done one the central site during agent
baking. Without the discovered host labels of remote site hosts, the bakery
could not compute the correct agent configuration for these hosts. The hosts
were not matched based on their discovered host labels.
This change now sets up a synchronization of discovered host labels from remote
sites to the central site for the bakery rules to be able to match the correct
hosts.
The synchronization is being executed on a regular base (every 10 minutes for
now) as background job. You can have a look at the state of this
synchronization at "Setup > Background jobs > Discovered host label
synchronization".
Change-Id: Id7112edf0f91a5d2c46d5bfd566defea0ec6b645
Commit: d2d946479b80497dcb720fc3c2f4bdf669d103c1
https://github.com/tribe29/checkmk/commit/d2d946479b80497dcb720fc3c2f4bdf66…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-03-30 (Tue, 30 Mar 2021)
Changed paths:
M cmk/gui/background_job.py
M cmk/gui/watolib/host_label_sync.py
M cmk/utils/labels.py
M tests/unit/cmk/utils/test_labels.py
Log Message:
-----------
Label synchronization can now gather discovered labels of a single host
The rule match analyzer of the ruleset editor needs have the discovered
host labels available locally. In this mode we know the site and host we
want to have the labels for and we want to enforce fetching the labels
of that host. This is the base for that operation mode.
Change-Id: I5d4c1066ef6c7189f3ef9651d2371b77847d6d55
Commit: c0778b0333fa06f937e323b7f4e794dcf429aeec
https://github.com/tribe29/checkmk/commit/c0778b0333fa06f937e323b7f4e794dcf…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-03-30 (Tue, 30 Mar 2021)
Changed paths:
A .werks/12554
M cmk/gui/wato/pages/rulesets.py
Log Message:
-----------
12554 FIX Ruleset editor: Fix analyzing host label matching in distributed setups
The ruleset editor provides a mode that allows a user to analyze the matching
of rules on specific hosts services. This mode analyzes the conditions configured
for a rule and reports whether or not these conditions match on the given host.
One of these conditions can be host labels. In distributed setups the host labels
are stored on the site the host is monitored from, while the analyzation of the
condition matching is being done on the central site.
If you have rules that have host labels configured as conditions, analyzing
the rule matching did not work because of the missing discovered host labels in
the central site.
This is now solved by synchronizing the host labels from the remote site to the
central site in the moment they are needed. This mechanism is based on the
synchronization mechanism that was introduced with werk #12553.
Change-Id: Icc7323c159bbec948c24c8d3672922723d1617d2
Commit: d16821abff731c193d6443d07eddc5a040763df5
https://github.com/tribe29/checkmk/commit/d16821abff731c193d6443d07eddc5a04…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-03-30 (Tue, 30 Mar 2021)
Changed paths:
A .werks/12555
M cmk/gui/plugins/views/sorters.py
Log Message:
-----------
12555 FIX Views: Fix crash when sorting hosts by IPv4 addresses
When trying to sort a host view by the IPv4 address column, an exception like
"TypeError ('>' not supported between instances of 'str' and
'tuple')" occurred
when the hosts to be sorted had mixed addreses (IPv4 addresses and host or DNS
names) configured.
Change-Id: If94a77f3d85519f7383896d2a08c1a9b4b7f12ee
Compare: https://github.com/tribe29/checkmk/compare/7ae5c009bf7b...d16821abff73