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.
ID: 14368
Title: site_management: New REST API endpoints implemented for distributed monitoring connections
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
This werk introduces the implementation of the site management endpoints. These endpoints
now allow the API user to create, delete, update and retrieve distributed monitoring
connection configurations. It's also possible to login to / logout of a remote site via
the endpoints. The new endpoints replace those from the Web-API. Client scripts should
be adjusted accordingly.
ID: 14751
Title: Fix general display options on service discovery page
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
If the options "This page without navigation" or "This page with navigation"
within the "Display" menu were used on the service discovery page, an error
like "Internal error: folder_path" occurred.
ID: 14752
Title: ServiceNow: Fix usage of custom description
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.2.0i1
The ServiceNow notification plugin always used the default for the host or
service description and the host or service short description.
ID: 14533
Title: azure agent: handle graph client errors gracefully
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The graph client API calls require some optional permissions so we are
handling these permissions errors by notifying the user of the issue but
by keeping the state to OK since it is a legit state.
The section that is impacted is the "azure_ad" one.
The message currently displayed is
"Graph client: Insufficient privileges to complete the operation." and
the permission that is currently needed is the Graph permission
"Directory.Read.All" that requires admin consent.
That permission needs to be granted to the check mk app created in Azure
during the setup of checkmk Azure monitoring.
ID: 14821
Title: Custom extensions might need adjustment due refactorings in GUI code (<tt>Transform</tt>)
Component: Setup
Level: 1
Class: New feature
Version: 2.2.0i1
This werk only affects users of non-tribe29 custom extensions (single files and MKPs from non-
tribe29 sources such as the Checkmk exchange).
Before this werk, the Checkmk codebase offered the <tt>ValueSpec</tt> subclass <tt>Transform</tt>,
which was used for two things:
LI: Changing the format in which configured values are stored (<tt>back</tt> and <tt>forth</tt>
specified).
LI: Updating legacy configurations to the current format (<tt>forth</tt> only specified).
As of this werk, the <tt>Transform</tt> class can only be used for the first point above (changing
the storage format). It now expects two mandatory arguments <tt>into_vs</tt> (previously
<tt>forth</tt>) and <tt>out_of_vs</tt> (previously <tt>back</tt>).
For updating legacy configurations, use the new <tt>Migrate</tt> class, which requires a mandatory
<tt>migrate</tt> argument. This is the equivalent of specifying <tt>forth</tt> only in the old
<tt>Transform</tt> class.