Werk 16562 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fix automatic host registration and removal in case one remote site is not logged in
key | value
---------- | ---
date | 2024-07-08T06:09:01+00:00
version | 2.3.0p10
class | fix
edition | cre
component | wato
level | 1
compatible | yes
The automatic host registration and removal jobs are executed regularly in the
background to add or remove hosts. These are fundamental mechanisms to the
automatic host registration.
The jobs failed completely in case one remote site was configured but not logged
in, not only affecting the not logged in site, but all sites. The not logged in
site is now being skipped, leaving the mechanism intact for all other sites.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Fix automatic host removal in case one remote site is not logged in
+ # Fix automatic host registration and removal in case one remote site is not logged in
? +++++++++++++++++
key | value
---------- | ---
date | 2024-07-08T06:09:01+00:00
version | 2.3.0p10
class | fix
edition | cre
component | wato
level | 1
compatible | yes
- The automatic host removal job is executed regularly in the background to remove
- hosts from the monitoring once they cease to exist. In particular for but not
- limited to automatically registered hosts.
+ The automatic host registration and removal jobs are executed regularly in the
+ background to add or remove hosts. These are fundamental mechanisms to the
+ automatic host registration.
- This job failed in case one remote site was configured but not logged in, not
? ^^ --------
+ The jobs failed completely in case one remote site was configured but not logged
? ^ + +++++++++++
- only affecting the not logged in site, but all sites. The not logged in site is
? --------
+ in, not only affecting the not logged in site, but all sites. The not logged in
? ++++++++
- now being skipped, leaving the mechanism intact for all other sites.
+ site is now being skipped, leaving the mechanism intact for all other sites.
? ++++++++
[//]: # (werk v2)
# Fix unknown services for Nutanix Prism
key | value
---------- | ---
date | 2024-07-10T14:20:49+00:00
version | 2.3.0p10
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a regression introduced in Checkmk 2.3.0p7 that caused several services to vanish during discovery or go to UNKNOWN during checking.
The affected plugins where
* Nutanix Prism: General Info about a Cluster
* Nutanix Prism: Cluster CPU
* Nutanix Prism: Host IO
* Nutanix Prism: Cluster Memory
[//]: # (werk v2)
# Fix sap_value check from crashing
key | value
---------- | ---
date | 2024-07-10T15:16:35+00:00
version | 2.3.0p10
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The `sap_value` check responsible for monitoring single SAP R/3 values
caused a crash during service discovery. With this werk, the cause of
the crash has been resolved.
[//]: # (werk v2)
# Fix unknown services for Nutanix Prism
key | value
---------- | ---
date | 2024-07-10T14:20:49+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a regression introduced in Checkmk 2.3.0p7 that caused several services to vanish during discovery or go to UNKNOWN during checking.
The affected plugins where
* Nutanix Prism: General Info about a Cluster
* Nutanix Prism: Cluster CPU
* Nutanix Prism: Host IO
* Nutanix Prism: Cluster Memory
[//]: # (werk v2)
# Add/Increase required password length for backup/agent key generation
key | value
---------- | ---
date | 2024-07-10T07:16:20+00:00
version | 2.4.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
When generating a encryption key for backups previously the length of the passphrase was not checked, therefore `a` would have been a valid passphrase.
In the enterprise and cloud edition it is possible to generate a agent signing key where a passphrase is required.
Here the passphrase needed to be at minimum 8 characters.
With this Werk both passphrases need to be at least 12 characters long.
This only applies to newly generated keys.
Already existing keys with shorter passphrases are still valid.
Also if you upload a key-pair the length is not checked, since re-encrypting keys can be complicated and usually company policies already apply.
[//]: # (werk v2)
# Fix sap_value check from crashing
key | value
---------- | ---
date | 2024-07-10T15:16:35+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The `sap_value` check responsible for monitoring single SAP R/3 values
caused a crash during service discovery. With this werk, the cause of
the crash has been resolved.
Title: password: the response schema now matches what is returned
Class: fix
Compatible: compat
Component: rest-api
Date: 1709803120
Edition: cre
Level: 1
Version: 2.2.0p31
This werk addresses an issue with the REST-API password endpoint
response. The response schema listed the title and the ident as
fields that should be returned but we were not returning them as
part of the password object. These have now been removed from the
schema.
Also, the members field was returning invalid information and
hence has been removed.
Title: missing error message for wrong backup key password
Class: fix
Compatible: compat
Component: wato
Date: 1719924608
Edition: cre
Level: 1
Version: 2.2.0p31
When a wrong password was entered for downloading a backup encryption key or a signature key for signing agents, an empty error message box was displayed.
Now, the error message is displayed correctly.