ID: 12478
Title: Automatic page refresh on graph collections and combined graphs
Component: metrics
Level: 1
Class: New feature
Version: 2.1.0i1
For users that constantly want to review a group of performance graphs on
the graph collections and combined graphs can now leave their page on
display and they will refresh automatically.
ID: 12378
Title: HW/SW Inventory: Do not show inventory tree of same-named hosts
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
It's possible to have same-named hosts on different, connected sites. If the
HW/SW Inventory is enabled on these hosts then the link to a host's inventory
tree view displays the trees of all same-named hosts on the same page.
In general it's not possible to display any of these inventory trees because
it's undecidable which inventory tree data belongs to which host: the host
inventory tree data was created locally or synced (eg. via liveproxyd). In this
case the data of the local host might have been overwritten by the remote one
(or the other way round).
ID: 12295
Title: View editor: Fix title of custom host attribute painter
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
The custom host attribute painter had the title of one of the custom attributes
"Hosts: My attribute title" in the column list instead of "Hosts: Host custom
attribute".
ID: 12307
Title: add cgroup v2 support for docker and lxc
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
The check_mk_agent executed inside a docker or lxc container on a host with
cgroup v2 enabled can now report metrics for cpu, memory and diskstat.
ID: 12354
Title: Uneditable WATO rules: <i>"You are trying to edit a rule which does not exist anymore."</i>
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
During cmk-update-config we re-write the WATO rules.
In case the transformation of a value of an individual rule failed,
we did not write the transformed rulesets at all. This lead to
rules that could not be edited (the reported error was
<i>"You are trying to edit a rule which does not exist anymore."</i>).
This could be mitigated by temporarily adding a new rule; after that
you could edit the pre-existing rules.
With this werk, we write the transformed rulesets even if the transformation
of single rules' values failed. That way, you can at least work with
all of the other rules, and replace the offending ones.
If this affects you, you can simply re-run cmk-update-config.
ID: 12357
Title: "Parameters for this service" was incomplete for clusters
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
The page <i>"Parameters of <HOST> / <service>"</i> showed
incomplete information if the host was a cluster.
The check parameters have been missing.
ID: 12229
Title: Fix bulk operations in host search
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If you searched for hosts via "Search hosts", any bulk operation, like e.g.
"Delete hosts", resulted in an error "No WATO folder //search".
ID: 12516
Title: Fixed state colors and overlapping texts in availability and timeline tables
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Availability tables showed state colors only on every other row. This has been fixed and the display of state colors has been unified with the common state color rendering that is known from views.
Also overlapping text glitches were fixed for availability and timeline tables.
ID: 12151
Title: Agent updater fails eventually when proxy environment is set on host
Component: agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In some rare cases, the agent updater may fail on hosts that have a proxy environment
configured. I.e., one of the environment variables <tt>HTTP_PROXY</tt>, <tt>HTTPS_PROXY</tt>,
<tt>ALL_PROXY</tt> (also lowercase variants) are set.
The agent updater will eventually fail with the following error message, which will be visible
at the <tt>cmk-update-agent.log</tt>:<br>
<tt>RuntimeError: dictionary changed size during iteration</tt>
This Werk is marked as incompatible, because there may be some manual action needed to
overcome this error:
If you are experiencing this error, you can temporarily unset the above mentioned environment
variable(s) on the affected systems in order to allow the agent updater to run properly and
to update itself to the fixed version. Alternatively, you can install a newly baked agent
on the system.