ID: 14560
Title: LIVESTATUS_TCP_ONLY_FROM now allows IPv6 addresses
Component: Site Management
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, using the command <tt>omd config set LIVESTATUS_TCP_ONLY_FROM</tt> with any IPv6 address
would fail. For example, the command
C+:
$ omd config set LIVESTATUS_TCP_ONLY_FROM "0.0.0.0 ::/0"
C-:
resulted in <tt>Invalid value for '0.0.0.0 ::/0'. Does not match allowed pattern.</tt>
With this werk, each IP address is matched using <tt>ipaddress.ip_network</tt> from the Python
standard library. In particular, this allows the usage of IPv6 addresses.
ID: 14474
Title: Fix parent renaming for hosts in subfolders
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
The renaming of hosts includes the renaming of parents, if the host that is
renamed is a parent of other hosts.
This renaming was faulty if the child host was in a subfolder that inherited
the parent attribute from a parent folder, leading to messages like "The parent
"FOO" of the host "BAR" is not defined on this site" on activation of changes.
Note that the parent was renamed correctly in the parent folder where the
attribute was effectivly set. Saving the folder properties again after renaming
fixed the mentioned error message.
ID: 14866
Title: Windows powershell plugins generate Utf-8 output by default
Component: Checks & agents
Level: 2
Class: New feature
Version: 2.2.0i1
Since this release, the output of all Windows powershell plugins
is configured as Utf-8 thus eliminating any problems with non-ASCII
symbols in the output.
ID: 14835
Title: mk_mongodb: Fix unknown option 'directConnection' which is only available since pymongo3.11
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
ID: 14754
Title: Fix search result on "Hosts" page if tags or labels are shown
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
If the inpage search on the page "Setup" - "Hosts" was used and the display
options "Show host tags" and/or "Show explicit host labels" were enabled, the
search result returned all hosts.
A workaround was to use the "... (show all)" link in the "Tags" column after
the search result returned. This only returned the matched hosts.
ID: 14558
Title: kemp_loadmaster_services: Missing Conns metric
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The active connections are now shown in the service graph, again.
ID: 14753
Title: Fix possible TypeError on views
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
If you used views like "Host groups" with column "Hosts colored according to
state" and without column "Host alias" an error like "TypeError: unhashable
type: 'list'" occurred.
ID: 14737
Title: Linux agent installation on systems with no-exec /var path
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
During agent package installation on Linux (.rpm or .deb package),
some shell scripts get executed that are located under the directory
<tt>/var/lib/cmk-agent</tt>.
This lead to problems, because on some environments, the /var directory
is mounted with noexec-flag and hence the scripts failed to execute.
To fix this situation, the installation scripts now get executed by
passing them to <tt>/bin/sh</tt>.
ID: 14738
Title: Linux agent: agent controller not in path when installing to non-default location
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
With the ruleset "Installation paths for agent files", you can choose non-default installation
directories for the Checkmk agent, including the path for executables.
While the chosen executable path should be in the <tt>PATH</tt> environment variable of target
systems, this is not guaranteed.
Previously, if it failed to be in the <tt>PATH</tt> within the context of the agent installation/update
with dpkg or rpm, the installation scripts failed to find the command <tt>cmk-agent-ctl</tt>, which
resulted in an inconsistent agent setup.
This situation is now fixed by executing the agent controller by its full (custom) path on agent
installation/update.
Please note that the affected script <tt>/var/lib/cmk-agent/super-server/setup deploy</tt> won't
be able to find the custom executable directory when called manually, so it will fall back to
<tt>/usr/bin/cmk-agent-ctl</tt> or just <tt>cmk-agent-ctl</tt>.
ID: 14802
Title: REST API user endpoints returns custom attributes
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
The endpoints to show a user like /objects/user_config/{userid} can now return set
custom attributes.