ID: 12857
Title: slack: Add option to configure proxy
Component: Notifications
Level: 1
Class: New feature
Version: 2.1.0i1
The option "HTTP proxy" was added for notification method "Slack or Mattermost".
ID: 12856
Title: ServiceNow: Clearer assignment in distributed environments
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
If ServiceNow notifications are used in distributed environments the host and
service problem ID might not be unique, because every site core creates own
host and service problem IDs. This could lead to problems with ticket creation
if the notifications end up at the same ServiceNow instance because the problem
ID might already have been used.
If you use such setup, please configure the new option "Use site ID prefix" in the
notification rule for ServiceNow. The notification script will then set the
host and service problem ID and the site name on creation.
If ServiceNow notifications are send from one site to one ServiceNow instance
or from different sites to different ServiceNow instances, no action is
required. The Script will use the old mechanism of setting and checking for
host and service problem IDs.
ID: 12683
Title: fileinfo_groups: No group patterns found for some enforced services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
If enforced services have been configured for fileinfo groups, there may be
instances in which the service returns an UNKNOWN status, along with the error
message "No group pattern found". This has been fixed.
ID: 12755
Title: Fix AssertionError if escalation is used in flexible notifications
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
If flexible notifications with option "Restrict to nth to mth notification
(escalation)" were used, notifications failed with an AssertionError in
notify.log.
ID: 12202
Title: f5_bigip_vserver: Crash when ip address invalid
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Check f5_bigip_vserver crashed when invalid ip address was sent.
Now, there is no crash and ip address is set as '-' (unknown).
ID: 12783
Title: inventory: kubernetes endpoint
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 2.1.0i1
Before this fix the inventory was 'OK' but showed:
WARNING: k8s_endpoint_info: failed: Unable to convert legacy results. Please migrate plugin to new API
This werk migrates the plugin to the new API
ID: 12807
Title: hp_msa: Fix TypeError: Unicode-objects must be encoded before hashing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The special agent hp_msa failed to connect with the error message
"TypeError: Unicode-objects must be encoded before hashing",
because the arguments were not encoded correctly.
This fix contains the conversion of the arguments to UTF-8.
ID: 12758
Title: notification replay not working and errors in the cmc.log
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
If a "Recent notification (for analysis)" in Setup -> Events -> Notifications
was replayed an error message was shown in the User interface. Furthermore,
the error message:
invalid signal byte ASCII 76, expected '*'
read 76 further bytes: 'oading autochecks from /omd/sites/stable/var/check_mk/autochecks/stable.mk
was logged in the cmc.log if a notification was sent. This is fixed.
ID: 12300
Title: Fix missing special agent in cluster configuration
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
<b>This fix is only necessary for Nagios.</b>
Clusters containing nodes with a special agent would crash with
the traceback
<tt>
File "/omd/sites/core/lib/python3/cmk/base/checkers/programs.py", line 266, in _make_source_args
info_func = config.special_agent_info[special_agent_id]
</tt>
because the special agent was missing from the configuration
of the cluster.