Werk 16659 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# ldap: allow manually updating locked status of users
key | value
---------- | ---
date | 2024-04-24T08:37:31+00:00
version | 2.3.0
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When using the "Authentication Expiration" sync plug-in for LDAP, users can be
stuck in a locked state after too many failed login attempts.
With this werk it is now allowed to edit the "Disable password" option in the UI
(or "disable_login" in the REST API) for users managed by LDAP. Please note that
a sync with the LDAP will restore the original value.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# ldap: allow manually updating locked status of users
key | value
---------- | ---
date | 2024-04-24T08:37:31+00:00
- version | 2.3.0b7
? --
+ version | 2.3.0
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When using the "Authentication Expiration" sync plug-in for LDAP, users can be
stuck in a locked state after too many failed login attempts.
With this werk it is now allowed to edit the "Disable password" option in the UI
(or "disable_login" in the REST API) for users managed by LDAP. Please note that
a sync with the LDAP will restore the original value.
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.0
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.0b7
? --
+ version | 2.3.0
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 16698 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# mknotifyd: Log to correct file after logrotate
key | value
---------- | ---
date | 2024-04-25T08:08:50+00:00
version | 2.3.0
class | fix
edition | cee
component | notifications
level | 1
compatible | yes
The logrotate cronjob rotated the logfile mknotifyd.log in the right way but
the mknotifyd was not aware of the changed logfile, resulting in logging to the
rotated file. The mknotifyd is now aware of a change of the logfile.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# mknotifyd: Log to correct file after logrotate
key | value
---------- | ---
date | 2024-04-25T08:08:50+00:00
- version | 2.3.0b7
? --
+ version | 2.3.0
class | fix
edition | cee
component | notifications
level | 1
compatible | yes
The logrotate cronjob rotated the logfile mknotifyd.log in the right way but
the mknotifyd was not aware of the changed logfile, resulting in logging to the
rotated file. The mknotifyd is now aware of a change of the logfile.
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.0
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.0b7
? --
+ version | 2.3.0
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 16692 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# inventory_primekey: do not crash upon empty node ID
key | value
---------- | ---
date | 2024-04-20T10:06:26+00:00
version | 2.3.0
class | fix
edition | cre
component | checks
level | 1
compatible | yes
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# inventory_primekey: do not crash upon empty node ID
key | value
---------- | ---
date | 2024-04-20T10:06:26+00:00
- version | 2.3.0b7
? --
+ version | 2.3.0
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Werk 16762 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# check certificates: fix signature algorithm configuration
key | value
---------- | ---
date | 2024-04-24T06:54:32+00:00
version | 2.3.0
class | fix
edition | cre
component | checks
level | 1
compatible | no
Upgrading from 2.3.0b4 to a later version could cause the _Check Certificates_ settings for signature algorithms to load incorrectly due to missing choices in the old settings.
This werk ensures correct loading.
This work is incompatible because some old algorithms are no longer available. Old configurations are converted as follows:
## rsa
- sha224: RSA_WITH_SHA224
- sha256: RSA_WITH_SHA256
- sha384: RSA_WITH_SHA384
- sha512: RSA_WITH_SHA512
- sha3_224: RSA_WITH_SHA224
- sha3_256: RSA_WITH_SHA256
- sha3_384: RSA_WITH_SHA384
- sha3_512: RSA_WITH_SHA512
## ecdsa
- sha224: ECDSA_WITH_SHA224
- sha256: ECDSA_WITH_SHA256
- sha384: ECDSA_WITH_SHA384
- sha512: ECDSA_WITH_SHA512
- sha3_224: ECDSA_WITH_SHA224
- sha3_256: ECDSA_WITH_SHA256
- sha3_384: ECDSA_WITH_SHA384
- sha3_512: ECDSA_WITH_SHA512
## rsassa_pss
Everything to RSASSA_PSS
## ed25519
ED25519
## dsa
- sha224: DSA_WITH_SHA224
- sha256: DSA_WITH_SHA256
- sha384: DSA_WITH_SHA256
- sha512: DSA_WITH_SHA256
- sha3_224: DSA_WITH_SHA224
- sha3_256: DSA_WITH_SHA256
- sha3_384: DSA_WITH_SHA256
- sha3_512: DSA_WITH_SHA256
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# check certificates: fix signature algorithm configuration
key | value
---------- | ---
date | 2024-04-24T06:54:32+00:00
- version | 2.3.0b7
? --
+ version | 2.3.0
class | fix
edition | cre
component | checks
level | 1
compatible | no
Upgrading from 2.3.0b4 to a later version could cause the _Check Certificates_ settings for signature algorithms to load incorrectly due to missing choices in the old settings.
This werk ensures correct loading.
This work is incompatible because some old algorithms are no longer available. Old configurations are converted as follows:
## rsa
- sha224: RSA_WITH_SHA224
- sha256: RSA_WITH_SHA256
- sha384: RSA_WITH_SHA384
- sha512: RSA_WITH_SHA512
- sha3_224: RSA_WITH_SHA224
- sha3_256: RSA_WITH_SHA256
- sha3_384: RSA_WITH_SHA384
- sha3_512: RSA_WITH_SHA512
## ecdsa
- sha224: ECDSA_WITH_SHA224
- sha256: ECDSA_WITH_SHA256
- sha384: ECDSA_WITH_SHA384
- sha512: ECDSA_WITH_SHA512
- sha3_224: ECDSA_WITH_SHA224
- sha3_256: ECDSA_WITH_SHA256
- sha3_384: ECDSA_WITH_SHA384
- sha3_512: ECDSA_WITH_SHA512
## rsassa_pss
Everything to RSASSA_PSS
## ed25519
ED25519
## dsa
- sha224: DSA_WITH_SHA224
- sha256: DSA_WITH_SHA256
- sha384: DSA_WITH_SHA256
- sha512: DSA_WITH_SHA256
- sha3_224: DSA_WITH_SHA224
- sha3_256: DSA_WITH_SHA256
- sha3_384: DSA_WITH_SHA256
- sha3_512: DSA_WITH_SHA256
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.0
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.0b7
? --
+ version | 2.3.0
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 16554 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# df: Wrong handling of lower levels for free space
key | value
---------- | ---
compatible | yes
version | 2.3.0
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.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# df: Wrong handling of lower levels for free space
key | value
---------- | ---
compatible | yes
- version | 2.3.0b7
? --
+ version | 2.3.0
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.
Werk 16780 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# APIDocs: missing ETag response header for 2 endpoints.
key | value
---------- | ---
date | 2024-04-24T14:41:14+00:00
version | 2.3.0
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.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# APIDocs: missing ETag response header for 2 endpoints.
key | value
---------- | ---
date | 2024-04-24T14:41:14+00:00
- version | 2.3.0b7
? --
+ version | 2.3.0
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 15845 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# winperf_if check correctly discovers and processes interfaces with spaces
key | value
---------- | ---
date | 2024-04-22T15:31:08+00:00
version | 2.3.0
class | fix
edition | cee
component | checks
level | 1
compatible | no
Previously, some Windows network interface names with additional spaces —
particularly before the hash symbol — were not recognized by the check engine.
This led to the absence of some services, especially Windows teaming network
interfaces.
In this release, such interface names are handled correctly thus fixing the
problem. Still, you may need to rediscover services again.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# winperf_if check correctly discovers and processes interfaces with spaces
key | value
---------- | ---
date | 2024-04-22T15:31:08+00:00
- version | 2.3.0b7
? --
+ version | 2.3.0
class | fix
edition | cee
component | checks
level | 1
compatible | no
Previously, some Windows network interface names with additional spaces —
particularly before the hash symbol — were not recognized by the check engine.
This led to the absence of some services, especially Windows teaming network
interfaces.
In this release, such interface names are handled correctly thus fixing the
problem. Still, you may need to rediscover services again.