Title: host: query on mk_inventory no longer causing crash
Class: fix
Compatible: compat
Component: rest-api
Date: 1706087872
Edition: cre
Level: 1
Version: 2.2.0p21
Previously, when you had a host that had no check running,
calling the following endpoint would cause a crash.
GET /domain-type/host/collections/all?columns=mkinventory
This werk addresses this issue by preventing the crash
and now returns an appropriate response.
[//]: # (werk v2)
# Event console: Fix missing customer if configured within rule packs
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-25T09:19:59+00:00
level | 1
class | fix
component | wato
edition | cme
If the customer field of a rule pack is configured then - after "save" - it's
gone. This bug was introduced with Checkmk 2.2.0 and has been fixed now.
[//]: # (werk v2)
# Fix tree of folders snapin filter for statistics dashlets
key | value
---------- | ---
date | 2024-01-24T09:17:40+00:00
version | 2.3.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | no
If you used the "Tree of folders" snapin and the shown dashboard contained a
dashlet "Host statistics" or "Service statistics" the wato folder was not
filtered for that dashlet.
[//]: # (werk v2)
# Fix error on edit of host or service statistics dashlet
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-24T14:06:42+00:00
level | 1
class | fix
component | multisite
edition | cre
If you edited the builtin dashlets "Host statistics" or "Service statistics" on
the main dashboard (CRE) / problem dashboard (CEE) you got an error like
"Internal error: size" on saving.
[//]: # (werk v2)
# Ensure site is stopped when running cmk-update-config
key | value
---------- | ---
date | 2024-01-23T11:58:49+00:00
version | 2.3.0b1
class | fix
edition | cre
component | core
level | 1
compatible | yes
The `cmk-update-config` command, which is usually executed as part of `omd
update` expects the site to be stopped during execution. This is always ensured
during `omd update`.
However, the command can also be executed manually later on. In this situation
the site can be running. To prevent unexpected results, the command now protects
against an accidentally running site on invocation.
[//]: # (werk v2)
# size_trend: avoid 'infinite to integer' crash
key | value
---------- | ---
date | 2024-01-24T14:08:45+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
While calculating how much time is left until the resource is full, if the value of the mb in range was too low (e.g. 1e-320) the check used to crash with 'infinite to integer'.
This has now been fixed and if the value is too low and causes division with it to result in 'inf', the check will not be executed.
[//]: # (werk v2)
# HW/SW Inventory: Improve displaying retention information
key | value
---------- | ---
date | 2024-01-24T11:35:45+00:00
version | 2.3.0b1
class | fix
edition | cre
component | inv
level | 1
compatible | yes
Fix missing retention information in views with HW/SW inventory columns. Do not
display retention icon if retention information is valid but not outdated.
[//]: # (werk v2)
# omd update: Fix setting world read permissions on etc and local files
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-19T18:46:45+00:00
level | 1
class | fix
component | omd
edition | cre
Starting with 2.2.0 (see #15062), we use a umask of 0077 to prevent files and directories owned by
the site user from being world readable. However, when updating from the CRE to a non CRE edition,
some files and directories were still set to be world readable during 'omd update'. This is now in
line with the other files.
[//]: # (werk v2)
# Fix wrong edition reported via livestatus in enterprise sites running the Nagios core
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-19T08:47:31+00:00
level | 1
class | fix
component | core
edition | cee
This change fixes a bug in the Nagios Core edition detection logic which could occur when using the
Nagios core with another edition than the Raw Edition. This is a rare use case, but can happen
temporarily during the migration from the Raw Edition to an Enterprise Edition.
The bug manifests itself by reporting the wrong edition via the livestatus interface. This can be
observed with the following query:
```
lq "GET status\nColumns: edition"
```
The edition column was introduced in 2.2.0.
Title: mk_redis: Use REDISCLI_AUTH instead of -a argument in order to hide password
Class: fix
Compatible: compat
Component: checks
Date: 1706088220
Edition: cre
Level: 1
Version: 2.1.0p39
mk_redis used to expose the password in the process name because of the '-a' argument.
This has been fixed using the environment variable REDISCLI_AUTH.