[//]: # (werk v2)
# APIDocs: missing ETag response header for 2 endpoints.
key | value
---------- | ---
date | 2024-04-24T14:41:14+00:00
version | 2.3.0b6
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
The following endpoints did not show that they returned an ETag header
as part of their 200 OK response.
* Show all pending changes
* Show password
This werk addresses this issue. Both now show the correct headers in
their responses.
Werk 14229 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic
key | value
---------- | ---
date | 2024-04-10T09:56:58+00:00
version | 2.3.0b7
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Normally, ListOf elements embedded in other ListOf elements should contain a different magic value, otherwise errors will occur when processing forms.
This werk here allows the use of identical magic values.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic
key | value
---------- | ---
date | 2024-04-10T09:56:58+00:00
- version | 2.3.0b6
? ^
+ version | 2.3.0b7
? ^
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Normally, ListOf elements embedded in other ListOf elements should contain a different magic value, otherwise errors will occur when processing forms.
This werk here allows the use of identical magic values.
Werk 16806 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Handle unexpected files in 'cmk_addons/plugins'
key | value
---------- | ---
date | 2024-04-23T12:04:08+00:00
version | 2.3.0b7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Checkmk 2.3.0 beta crashed during various operations if unexpected files where
put into `local/lib/python3/cmk_addons/plugins/` or `local/lib/python3/cmk/plugins/`.
They are ignored now.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Handle unexpected files in 'cmk_addons/plugins'
key | value
---------- | ---
date | 2024-04-23T12:04:08+00:00
- version | 2.3.0b6
? ^
+ version | 2.3.0b7
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Checkmk 2.3.0 beta crashed during various operations if unexpected files where
put into `local/lib/python3/cmk_addons/plugins/` or `local/lib/python3/cmk/plugins/`.
They are ignored now.
Werk 14230 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# BI: Fixed incorrect aggregation of downtimes
key | value
---------- | ---
date | 2024-04-10T12:05:48+00:00
version | 2.3.0b7
class | fix
edition | cre
component | bi
level | 1
compatible | yes
The configuration option <tt>Escalate downtimes based on aggregated WARN state</tt> did not correctly since version 1.5.
The behaviour is now fixed and works like its mentioned in our [official documentation](https://docs.checkmk.com/latest/en/bi.html#_tuning_options)
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# BI: Fixed incorrect aggregation of downtimes
key | value
---------- | ---
date | 2024-04-10T12:05:48+00:00
- version | 2.3.0b6
? ^
+ version | 2.3.0b7
? ^
class | fix
edition | cre
component | bi
level | 1
compatible | yes
The configuration option <tt>Escalate downtimes based on aggregated WARN state</tt> did not correctly since version 1.5.
The behaviour is now fixed and works like its mentioned in our [official documentation](https://docs.checkmk.com/latest/en/bi.html#_tuning_options)
Werk 16697 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ignore empty "Multiple sites" filter if "Site" filter is set
key | value
---------- | ---
compatible | yes
version | 2.3.0b7
date | 2024-04-23T06:07:04+00:00
level | 1
class | fix
component | multisite
edition | cre
If both filters "Multiple sites" and "Sites" were set, the "Multiple sites"
filter was used, even if empty.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ignore empty "Multiple sites" filter if "Site" filter is set
key | value
---------- | ---
compatible | yes
- version | 2.3.0b6
? ^
+ version | 2.3.0b7
? ^
date | 2024-04-23T06:07:04+00:00
level | 1
class | fix
component | multisite
edition | cre
If both filters "Multiple sites" and "Sites" were set, the "Multiple sites"
filter was used, even if empty.
+
Werk 16682 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Fix migration with scaling of SimpleLevels
key | value
---------- | ---
date | 2024-04-17T11:19:36+00:00
version | 2.3.0b7
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is relevant to plugin developers
The migration helper functions `migrate_to_integer_simple_levels` and `migrate_to_float_simple_levels` for `SimpleLevels` currently apply the scaling factor (if given) every time the migration is run, meaning also to the already migrated value.
This means any rule where these helpers are used with a scaling factor will have incorrect values and will have to be manually corrected.
No shipped rules are affected by this.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Fix migration with scaling of SimpleLevels
key | value
---------- | ---
date | 2024-04-17T11:19:36+00:00
- version | 2.3.0b6
? ^
+ version | 2.3.0b7
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is relevant to plugin developers
The migration helper functions `migrate_to_integer_simple_levels` and `migrate_to_float_simple_levels` for `SimpleLevels` currently apply the scaling factor (if given) every time the migration is run, meaning also to the already migrated value.
This means any rule where these helpers are used with a scaling factor will have incorrect values and will have to be manually corrected.
No shipped rules are affected by this.
[//]: # (werk v2)
# Handle unexpected files in 'cmk_addons/plugins'
key | value
---------- | ---
date | 2024-04-23T12:04:08+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Checkmk 2.3.0 beta crashed during various operations if unexpected files where
put into `local/lib/python3/cmk_addons/plugins/` or `local/lib/python3/cmk/plugins/`.
They are ignored now.
[//]: # (werk v2)
# Synthetic monitoring: Fix crash in "Robotmk scheduler (Windows)" bakery rule when attempting to save with invalid settings
key | value
---------- | ---
date | 2024-04-24T12:38:16+00:00
version | 2.3.0b7
class | fix
edition | cee
component | setup
level | 1
compatible | yes
When attempting to save the bakery rule "Robotmk scheduler (Windows)" with invalid settings such as
an empty base directory or an invalid application name, the UI page crashed with
<code>TypeError: argument of type 'NoneType' is not iterable</code>.
[//]: # (werk v2)
# df: Wrong handling of lower levels for free space
key | value
---------- | ---
compatible | yes
version | 2.3.0b7
date | 2024-04-19T12:35:12+00:00
level | 1
class | fix
component | checks
edition | cre
This is a regression since Checkmk 2.2.0.
When configuring the Service Monitoring Rule "Filesystems (used space and growth)",
configured levels for free space were evaluated incorrectly.
As a result, affected services erroneously showed up as *CRIT*.
This happened because of a wrong rounding while evaluating the levels, and only affected
small filesystems with a size below 1MB.