ID: 14287
Title: Fix another source for frozen Microcore during config reloads (Addition to #14285)
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
In addition to the werk #14285 we released with 2.1.0p8, this werk fixes
another situation which could block the reload of the Microcore.
This could happen in case you have notification rules configured which use the
match condition "Match only during timeperiod".
ID: 14379
Title: Change how secrets are masked for logging
Component: Setup
Level: 1
Class: New feature
Version: 2.2.0i1
When changing rules that contain passwords or SSH private keys, those secrets are now masked as '*' characters instead of hashes in the audit log.
ID: 14528
Title: SAP HANA backup check in cluster mode: go stale if cannot connect to DB
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Before this werk, if the connection to a database failed, the SAP HANA
Backup service in a cluster host was marked as OK.
This is now changed and the service goes stale.
ID: 14454
Title: "NetApp Filer: Used Space of LUNs" supports magic factor
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
The plugin "NetApp Filer: Used Space of LUNs" (<tt>netapp_api_luns</tt>) now supports the configuration of the magic factor in its ruleset <i>"NetApp LUNs"</i>.
ID: 14146
Title: Rule matching for hosts
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
The search for host rules in Setup did not work as expected when matching host regex conditions.
The issue did not affect the rule matching visualization nor the actual rule matching.
When checking the matching rules for hosts the rules with regular expressions
would not get a green background although the regex should match, which indicates
the rule is not matching the current search.
Now the rule matching is fixed and the rules will get a green background if they match the search.
ID: 14499
Title: activate changes: performance issues when synchronising users and user settings
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
The activate changes process could be slow when activating changes for multiple
sites in a distributed monitoring set-up. The activation would eventually run
into an error similar to "Failed to start activation [502]: Proxy Error". This
was due to the implementation that synchronises users and user settings across
all sites. Instead of copying these files in their entirety, a hard link is now
created, reducing I/O on the monitoring server.
ID: 14286
Title: mail: Add timeout to graph processing of HTML mail notifications
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.2.0i1
In case fetching the graphs takes more than 10 seconds, the notification plugin
aborts waiting for the graphs and continues to send the notification without
graphs.
ID: 14285
Title: Fix frozen Microcore (Livestatus not responding) during config reloads
Component: Core & setup
Level: 2
Class: Bug fix
Version: 2.2.0i1
The reload of the Microcore core and it's helper processed could freeze when
the core had notifications pending during reload. This was caused by a deadlock
between the Notification helper and the Microcore. The Microcore was still
alive but waiting to the notification helper to terminate while the
notification helper waited for the Microcore.
>From the user perspective this resulted in Livestatus not being responsive
while the cmc.log showed a message like: <tt>still X unsent events, sending
them now</tt>.
ID: 14602
Title: cmk-update-agent: Use configured var directory
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The agent updater used to use the fixed directory <tt>var/lib/check_mk_agent/</tt>
to unpack its CA certificates regardless of what was configured in the rule
"Installation paths for agent files"
Technically spoken, this means that the agent updater now respects
the <tt>MK_VARDIR</tt> environment variable.