Title: win_os: Add HW/SW inventory field 'version'
Class: fix
Compatible: compat
Component: checks
Date: 1698134267
Edition: cre
Level: 1
Version: 2.3.0b1
For Windows hosts we use the 'caption' field for the HW/SW inventory 'version'
field but without the prefix 'Microsoft', eg.:
'Microsoft Windows Server 2008 R2 Standard' -> 'Windows Server 2008 R2 Standard'
Title: nfsiostat: fix units and parsing
Class: fix
Compatible: compat
Component: checks
Date: 1698239388
Edition: cre
Level: 1
Version: 2.3.0b1
Units falsely displayed seconds, although milliseconds are corret.
Newer versions of nfsiostat output more data, this confused our parser.
Title: Speed up "Extension packages" pages
Class: fix
Compatible: compat
Component: wato
Date: 1697744735
Edition: cre
Level: 1
Version: 2.3.0b1
The pages of the "Extension packages" manager where loading
slowly for sites with many local files.
Title: sap_hana_db_status: Be ok for passive nodes
Class: fix
Compatible: compat
Component: checks
Date: 1698058635
Edition: cre
Level: 1
Version: 2.3.0b1
The service <i>"SAP HANA Database Status"</i> went critical on a passive node.
In now remains ok and reports <i>"System is in passive mode"</i>.
Title: Mega menu: Hide "Customize" menu and menu items for users with no permission
Class: feature
Compatible: compat
Component: wato
Date: 1698216784
Edition: cre
Level: 1
Version: 2.3.0b1
Before this Werk, users without permissions to access the "Customize" menu could still see it in the mega menu,
and then when accessing it they would get an error message. This Werk fixes that behaviour by hiding the menu
entries to which the user does not have access, or the entire menu in case the user does not have any
customisation permissions.
Werk 16127 was deleted. The following Werk is no longer relevant.
Title: agent-updater change behaviour of trust-cert option
Class: fix
Compatible: compat
Component: agents
Date: 1695817306
Edition: cee
Knowledge: doc
Level: 1
Version: 2.3.0b1
When registering the agent-updater and using the <tt>--trust-cert</tt> option the agent-updater used to traverse the certificate-chain and trust the first self-signed certificate in the chain which is usually a CA.
Unfortunately this relied on the server to provide the full certificate chain.
It is not uncommon to only provide the certificate and the corresponding intermediate CA certificate.
In these scenarios the agent-updater failed to trust the certificate.
Also the help text indicates that only the server certificate is trusted.
With this Werk the agent-updater retrieves the certificate of the server and trusts just that certificate.
Caution: If your registration workflow relies on an initial registration with <tt>--trust-cert</tt> option and you don't provide a certificate via another channel (see https://docs.checkmk.com/latest/en/agent_deployment.html#provide_certificat…), you'll now lose trust when changing the Checkmk server's server certificate.
If your workflow relies on the <tt>--trust-cert</tt> option, please make sure to provide a valid certificate via the agent updater ruleset or via global settings.
Title: agent-updater change behaviour of trust-cert option
Class: fix
Compatible: compat
Component: agents
Date: 1695817306
Edition: cee
Knowledge: doc
Level: 1
Version: 2.3.0b1
When registering the agent-updater and using the <tt>--trust-cert</tt> option the agent-updater used to traverse the certificate-chain and trust the first self-signed certificate in the chain which is usually a CA.
Unfortunately this relied on the server to provide the full certificate chain.
It is not uncommon to only provide the certificate and the corresponding intermediate CA certificate.
In these scenarios the agent-updater failed to trust the certificate.
Also the help text indicates that only the server certificate is trusted.
With this Werk the agent-updater retrieves the certificate of the server and trusts just that certificate.
Caution: If your registration workflow relies on an initial registration with <tt>--trust-cert</tt> option and you don't provide a certificate via another channel (see https://docs.checkmk.com/latest/en/agent_deployment.html#provide_certificat…), you'll now lose trust when changing the Checkmk server's server certificate.
If your workflow relies on the <tt>--trust-cert</tt> option, please make sure to provide a valid certificate via the agent updater ruleset or via global settings.
Title: cisco_webex_teams: Fix failed notification on response code 204
Class: fix
Compatible: compat
Component: notifications
Date: 1697549543
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p13
The notification script produced a failed notification, even if the processing was successful.