ID: 12846
Title: Fix inheritance of folder contact groups to services of hosts
Component: Setup
Level: 2
Class: Bug fix
Version: 2.1.0i1
The assignment of contact groups to hosts and services can be controlled using
the folder hierarchy of WATO as described in the user manual
(https://docs.checkmk.com/latest/en/wato_user.html#_allocation_via_folders).
You are only affected by this change in case you use a) the WATO folder hierarchy
for assigning contact groups to services.
When using the assigning contact groups to services with the following
settings, this could result in too many groups being assigned to a service:
<ul>
<li>Add these groups as contacts to all hosts in this folder: Enabled</li>
<li>Add these groups as contacts to all hosts in all subfolders of this folder: Not enabled</li>
<li>Always add these groups as contacts to all services in all subfolders of this folder: Enabled</li>
</ul>
In this situation only the groups from the nearest parent folder should be
assigned to the services, just like it is done for the hosts. Instead the
services got the groups assigned from all parent folders which have the
service assignement enabled.
We now have changed the contact groups of the services to be handled exactly
like the hosts. Only the contact groups defined in the nearest parent folder
with the service assignment enabled will be added to the services.
Example:
<code>
Folder_A (Permission: group1, settings as listed above)
|_Folder_B (Permission: group2, settings as listed above)
</code>
In this scenario, a host in the Folder_B gets the contact group "group2"
assigned. Services got the "group1" and "group2" assingned in previous
versions. Now the services get the "group2" assigned, just like the host.
ID: 13086
Title: Log error messages from the ICMP sender again.
Component: cmc
Level: 2
Class: Bug fix
Version: 2.1.0i1
The CMC didn't pick up any error messages from the ICMP sender, which could
in turn result in blocking the sender. This was a regression from 1.6.0.
ID: 12175
Title: Postpone notifications for passively checked objects, too.
Component: cmc
Level: 2
Class: Bug fix
Version: 2.1.0i1
Even when a host is down, we can still receive check results for passive
checks on that host, e.g. via the piggyback mechanism. Any notifications
resulting from these check results should be postponed in the normal way,
too.
ID: 12325
Title: Stabilize Windows Agent RunAs(User/Group) plugin feature
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 2.1.0i1
Previously, Windows agent supplied as working directory the current one.
This may lead to failure if the starting plugin in RunAs mode had being
executed from the account without valid access rights.
Since this release the problem has been eliminated. If a plugin is starting
in RunAs mode, then Windows Agent supplies to the starting plugin user home
directory as a working directory.
ID: 12324
Title: Windows WMI timeout is increased to improve stability of WMI queries
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 2.1.0i1
This change is intended to seriously reduce the number of undesired timeouts
during the access to the WMI on heavily loaded systems.