ID: 12738
Title: Skip empty values on bulk host import via CSV file
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If values were missing for some hosts and this kind of value was selected in
preview, e.g. "IPv4 address", importing was not possible because of a
validation error.
Such values are now skipped. The affected hosts are now imported without the
missing value.
ID: 12314
Title: checks: Fix "MS Exchange Information Store" rule crash
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The checks msexch_isclienttype and msexch_isstore crashed with
"AttributeError: 'tuple' object has no attribute 'get'"
if the rule "MS Exchange Information Store" existed. This should now be fixed.
ID: 12500
Title: Call parse function even for empty data
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
This change only affect users with own SNMP section plugins
developed against the *new* API.
Previously the parse function of an SNMP section (or SNMP
check plugin) has only been called if at least *some* data
could be fetched from the host (the SNMP device).
In the old API (Checkmk version < 2.0) this behaviour
could be changed by setting the 'handle_empty_info' key -
only then would the parse function be called for empty
data.
The new API will *allways* call the parse function, if
the sections raw data is present in the fetched data (even
if it is empty). It is the programmers responsibility to
deal with an potentially empty data set.
This allows for a subtle distiction: If the parse function
returns `None`, no further processing is done, it is
regarded as 'not present'. An empty return value could
represent some valid information, such as an empty list
of error messages.
Note that this behaviour is consistent with the TCP data
sources' sections, where we also may encounter sections
that are present, but empty.
ID: 12501
Title: apc_inrow_system_events,liebert_system_events,printer_alerts: Services were not discovered
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The services of the check plugins <tt>apc_inrow_system_events</tt>,
<tt>liebert_system_events</tt> and <tt>printer_alerts</tt> could not
be discovered if no events or alerts were present (i.e. almost never).
This is fixed.
ID: 12502
Title: Rare bug during parsing for clustered custom plugins
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
This werk only affects users that have certain custom plugins
developed against the old check API in a clustered setup.
Specificly: This affects you, if you have
<ul>
<li>a custom check plugin</li>
<li>using the <i>*_item_state</i> features <b>in the parse function</b></li>
<li>in a clustered service setup</li>
</ul>
In this case, you probably observed crashes of the parse function or
stale services (we have never observed this theoretical bug).
This will be fixed. However: If this actually affected you, you should
consider moving all <i>item_state</i> related logic into the check
function (as this will be enforced by the new API).
ID: 11800
Title: Avoid escaping in custom host attributes
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
In case custom host attributes where containing special characters (e.g. "&"), they where stored escaped on disk
and therfore also displayed escaped in the GUI.
This fix is applied during <tt>omd update</tt>, so no manual interaction is needed when updating to this patchlevel.
ID: 12625
Title: Fix invalidation of session on logout
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If the global setting "Limit login to single session at a time" was used, the
session was not correctly invalidated on logout. The user was not able to do a
login again until the configured session timeout was met.
ID: 12195
Title: site_object_counts: Error when site object empty
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Check site_object_counts failed when there was an empty site object.
Empty site objects are no longer discovered.
ID: 12692
Title: k8s_replicas: proper check message when replicas data is not available
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In some instances, the Kubernetes replicas information is either incomplete or
not available. The unavailability is usually of short period. In the previous version,
this led to failure of the check. This werk introduces a mechanism to handle this event.
The check initially goes into a stale state before displaying a crit status if the data
is unavailable for more than 10 minutes.
ID: 12193
Title: ps: Metrics for oldest and youngest process age
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Metrics and graphs added for oldest and youngest process age.