ID: 14080
Title: Fix synchronisation of password store to customer sites
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
Any password synchronised from a central to a remote customer site was empty.
For this fix to come into effect, users have to open a stored password in the
central site, save the password (no modification needed) and activate the
resulting changes.
ID: 14328
Title: Fix host search with option "Locked by"
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
The host search returned no search results if option "Locked by" was used, even
if host would match.
For example, this search is used in the dynamic host management action "Hosts
assigned with this connection".
ID: 14326
Title: Fix PDF export of views with context / search filters
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 2.2.0i1
If views with context / search filter defined were exported via "Export this
view as PDF", the filter were ignored.
Only filter used with the "Filter" option of the view were taken into account.
ID: 13683
Title: Solaris agent update removes services symlink
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
When updating agents using the agent updater on Solaris, the postremove script
will try to remove the corresponding service line from <tt>/etc/services</tt>.
However, the script recently missed the fact that this usually is a symbolic
link to the actual services file, and overrode it with a new (hardlinked) file.
Moreover, this situation could lead to a missing Checkmk agent service, as the
situation got cleaned up on calls to <tt>pkg verify</tt> and <tt>pkg fix</tt>
by replacing the <tt>/etc/services</tt> file with the proper symbolic link
again, locking out the Checkmk agent.
This Werk is marked as incompatible, because some additional action might be
required to finally fix the state on your Solaris hosts. The uninstallation
script now preserves an existing symlink, but can't clean up an overridden
link. When setting the symlink back to its proper target manually while the
Checkmk agent is installed, be sure to paste the line containing
<tt>check-mk-agent</tt> to the target file in advance.
ID: 14352
Title: use sentence case for local check metric labels
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Since werk 12185 we automatically show metrics in the output of local checks. The metric names
are now consistently converted to sentence case. Below are examples for the automatic conversion
LONG_METRIC_NAME -> Long metric name
recommendation4WHO -> Recommendation 4 WHO
weekIncidence -> Week incidence
zombie_apocalypse -> Zombie apocalypse
ID: 14330
Title: Fix possible ValueError on dashboards after update to 2.1
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
If dashboards were created with a custom topic in version 2.0, the error
"ValueError (invalid literal for int() with base 10: '')" could occur after
updating to 2.1.
Possible workaround was to change the topic of the affected dashboard to a
builtin topic and run "cmk-update-config" as site user again. The dashboard
should be ok after that and you can change back to the custom topic.
ID: 13923
Title: Dashboard elements: Fix title macros
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
The macros $HOST_NAME$ and $SERVICE_DESCRIPTION$ which can be used in the custom title of dashboard elements were without function. This is fixed: Whenever context information about host name or service description is available, the respective macro is replaced by this context information.
ID: 14371
Title: Fix AWS special agent crash for EC2 missing tags
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk fixes a crash in the AWS special agent that was happening
when filtering EC2 instances by AWS tag with EC2 limits enabled.
ID: 13422
Title: Don't show cluster checks for standalone FortiGate
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The services "Cluster Info", "CPU utilization Cluster", "Memory Cluster" and
"Sessions Cluster" where discovered even if the FortiGate device was in
standalone mode. Those services will no longer be discovered.