ID: 14076
Title: Alertmanager special agent: Handle credentials from password store correctly
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The Alertmanager special agent did not handle credentials from the password
store correctly, leading to connection failures.
ID: 14078
Title: Fix deletion of users with none-ASCII characters in distributed setups with configuration replication
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
In distributed setups with configuration replication, deleting a user with none-ASCII
characters in its username led to a crash upon attempting to activate the change:
<tt>cmk.gui.exceptions.MKUserError: The given text must only contain ASCII characters.</tt>
ID: 14077
Title: NagVis Geomaps: Deprecate <tt>wato_geo_fields.py</tt> in favor of regular custom host attributes
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk only affects users of NagVis Geomaps.
One of the available map types in NagVis are Geomaps, which show geographical locations.
For this map type, NagVis offers the option to use geographical coordinates stored in
Checkmk host attributes, see http://docs.nagvis.org/1.9/en_US/geomap.html.
The necessary host attributes (latitude and longitude) are by default not available in
Checkmk. Therefore, up to now, Checkmk came with the script
<tt>share/doc/check_mk/treasures/wato_geo_fields.py</tt>,
which added these host attributes.
As of this werk, <tt>wato_geo_fields.py</tt> is deprecated, since it is incompatible
with Checkmk 2.1. Attempting to use this script in version 2.1 will fail, meaning that
latitude and longitude will no longer available in the user interface. Furthermore, the
REST API will respond with HTTP 500 when attempting to query the status of affected
hosts.
To retain the functionality previously offered by this script, users can instead create
two regular custom host attributes. This is fully compatible and will not result in any
loss of data. The exact procedure is described here:
https://kb.checkmk.com/display/KB/Geo+coordinates+from+Checkmk+in+NagVis+ma….
After creating the custom attributes, users must remove their local copy of
<tt>wato_geo_fields.py</tt> from <tt>local/share/check_mk/web/plugins/wato/<tt>.
ID: 14256
Title: REST-API objects/ruleset: Change status code to 404 when ruleset doesn't exist
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
The objects ruleset endpoint previously returned a 500 internal server error when
the ruleset didn't exist. This werk changes the status code to a 404 'Unknown ruleset'
ID: 13420
Title: Fix section parsing with different separators
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
In checkmk it's possible to transport a single section with different separators:
<code>
<<<section:sep(44)>>>
a,1
<<<section:sep(124)>>>
b|2
<<<section:sep(44)>>>
c,3
</code>
Up until this werk, the ordering of the lines where not preserved, the check
function would have received them as a,1 c,3 b,2
ID: 13944
Title: Title: Long text in the inventory dashlet will now break into multiple lines
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
Instead of rendering the text of the inventory dashlet on one line,
the text will now break into multiple lines if not enough space is there.
ID: 14094
Title: Permission error during agent controller installation
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
A regression in Checkmk 2.1.0b9 could lead to a permission error during the installation of the Checkmk agent.
ID: 13724
Title: Remove legacy macro expansion in Event Console script actions
Component: Event Console
Level: 2
Class: Security fix
Version: 2.2.0i1
The Event Console is able to execute actions, e.g. shell scripts, when opening
or cancelling events. Details of the events are available to the script via
environment variables <tt>CMK_</tt> as described in the user manual
(https://docs.checkmk.com/latest/en/ec.html#_shell_scripts_and_emails). This
mechanism will keep working as before.
However, there is a second undocumented mechanism which relies on macro
expansion in the shell scripts. Previously it was possible to use macros (e.g.
<tt>$HOST$</tt>) in the <i>Event Console</i> scripts. These were replaced
before executing the script. The values of these macros can be untrusted input
and lead to command injections. You are only affected by this issue, if your
scripts use the macro expansion.
With this incompatible change we remove the macro expansion mechanism for
security reasons. The site update mechanism tries to detect Event Console
actions using these macros, disables the actions and informs you about this
change. The output of an <tt>omd update</tt> for a rule being disabled would
look like this:
C+:
"Script 'some_action_id' uses macros. We disable it. Please replace the macros
with proper variables before enabling it again!"
C-:
If you use the <i>Event Console</i> with shell script actions you should check
your scripts for macros and replace them with the documented environment
variable approach (Setup > Events > Event Console rule packs > Event Console
configuration > Event Console configuration). You can access all macro values
with environment variables (they are prefixed with <tt>CMK_</tt>).