Title: downtimes: can now delete downtimes from remote sites
Class: fix
Compatible: compat
Component: rest-api
Date: 1699869696
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p15
As a result a previous change to the downtimes delete endpoint,
we introduced a bug which prevented downtime deletion on
remote sites.
This werk addresses this issue. Downtimes on remote sites are now
deleted as expected.
Title: Enable update as site user due incompatible python versions
Class: fix
Compatible: compat
Component: omd
Date: 1699525492
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p14
This werk is relevant for you in case you've been using <tt>omd -V {version} update</tt> as site user.
Due to the update of the Python version from 3.11.2 to 3.11.5 with 2.2.0p13, we needed to introduce a fix in order to avoid the following issue:
C+:
Traceback (most recent call last):
File "/omd/versions/2.2.0p13.cee/bin/omd", line 60, in <module>
import omdlib.main
File "/omd/versions/2.2.0p13.cee/lib/python3/omdlib/main.py", line 36, in <module>
import random
File "/omd/versions/2.2.0p13.cee/lib/python3.11/random.py", line 49, in <module>
from math import log as _log, exp as _exp, pi as _pi, e as _e, ceil as _ceil
ImportError: /omd/versions/2.2.0p13.cee/lib/python3.11/lib-dynload/math.cpython-311-x86_64-linux-gnu.so: undefined symbol: _PyModule_Add
C-:
However, this fix introduced another issue with the release of 2.2.0p13, that's why we had to withdraw 2.2.0p13 and release 2.2.0p14 which addressed both issues.
Werk 16192 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Licensing: Distributed monitoring overview during update
Class: fix
Compatible: compat
Component: multisite
Date: 1699368840
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p14
When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1.
The site status will now display correctly.
------------------------------------<diff>-------------------------------------------
Title: Licensing: Distributed monitoring overview during update
Class: fix
Compatible: compat
Component: multisite
Date: 1699368840
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p14
- When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1.
? ^ ^
+ When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1.
? ^^^^ ^^^^
The site status will now display correctly.
-
-
Title: host_config: can now move host between nested folders
Class: fix
Compatible: compat
Component: rest-api
Date: 1699258683
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p15
This werk addresses an issue discovered when moving hosts to folders
that were more than one folder deep. Previously, the possible target
folders for the given host were incorrectly checked. We now have
a fix which will correctly check first if the target folder is
permitted.
Werk 16192 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Licensing: Distributed monitoring overview during update
Class: fix
Compatible: compat
Component: multisite
Date: 1699368840
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p14
When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1.
The site status will now display correctly.
------------------------------------<diff>-------------------------------------------
Title: Licensing: Distributed monitoring overview during update
Class: fix
Compatible: compat
Component: multisite
Date: 1699368840
Edition: cre
Knowledge: doc
Level: 1
- Version: 2.2.0p15
? ^
+ Version: 2.2.0p14
? ^
When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1.
The site status will now display correctly.
Werk 16215 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: agent_elasticsearch: resolve error when requesting indices stats
Class: fix
Compatible: compat
Component: checks
Date: 1699277518
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p14
There is a special error case which arises when trying to request the
indices stats from Elasticsearch which has at least one alias
pointing to a closed index. In the previous version, the special agent
completely failed in such scenarios. This werk resolves this by
requesting only the accessible indices.
------------------------------------<diff>-------------------------------------------
Title: agent_elasticsearch: resolve error when requesting indices stats
Class: fix
Compatible: compat
Component: checks
Date: 1699277518
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
- Version: 2.2.0p15
? ^
+ Version: 2.2.0p14
? ^
There is a special error case which arises when trying to request the
indices stats from Elasticsearch which has at least one alias
pointing to a closed index. In the previous version, the special agent
completely failed in such scenarios. This werk resolves this by
requesting only the accessible indices.
Title: Licensing: Distributed monitoring overview during update
Class: fix
Compatible: compat
Component: multisite
Date: 1699368840
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p15
When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1.
The site status will now display correctly.
Title: cisco_ucs_mem: check for memory faults
Class: feature
Compatible: compat
Component: checks
Date: 1700038826
Edition: cre
Level: 1
Version: 2.3.0b1
As of this werk, the plugin additionally checks and reports memory faults reported by the device.
Acknowledged faults will be reported as OK. Otherwise, the monitoring state depends on
the fault severity: "major" and "critical" are reported as CRITICAL, "warning" and
"minor" as WARNING and "cleared" and "info" as OK.
Title: Resolve Runas section in Checkmk Linux agent
Class: fix
Compatible: compat
Component: checks
Date: 1699515827
Edition: cre
Level: 1
Version: 2.3.0b1
Prior to this werk, the Runas section of the Checkmk agent
contained a wrong trailing slash which resulted in an error
with the find command. As a direct consequence, some or
potentially all Runas rules were inadvertently ignored, leading
to the plugin, not intended for root, being executed with root
privileges. This werk fixes this behaviour.
Title: Ignore piggybacked host names starting with a period
Class: fix
Compatible: incomp
Component: core
Date: 1699602114
Edition: cre
Level: 1
Version: 2.3.0b1
We now skip piggybacked data for hosts names starting
with a period. Examples of such invalid names are ".",
".hostname", and ".hostname.domain.com".
Users must rename such hosts if they should remain
in the monitoring.