Title: agent_kube: resolve case when referenced PVC is no longer present
Class: fix
Compatible: compat
Component: checks
Date: 1714992435
Edition: cre
Level: 1
Version: 2.2.0p27
Prior to this werk, the Kubernetes special agent failed whenever
the API returned Kubernetes objects with at least one reference
to a no longer existing PVC. This werk fixes this issue by ignoring
such references.
[//]: # (werk v2)
# Changed aborting behavior for overrunning cached agent plugins
key | value
---------- | ---
date | 2024-05-03T09:42:12+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This Werk changes the exact condition under which the Unix agents kill long running cached agent plugins.
Affected are the Checkmk agent plugins for Linux, AIX, Solaris, OpenWrt and FreeBSD.
### Previous behavior
Any agent plugin that ran for more that twice its caching interval _without generating output_ was killed by the agent. The agent checked for this every minute.
### New behavior
Any agent plugin running for more than twice its caching interval will be killed.
It is no longer relevant wether the plugin produces output during that time.
The killing is done from within the asynchronous process itself, eliminating any potential danger of inadvertently killing the wrong process.
[//]: # (werk v2)
# cmk-update-config: Improve Handling of Implementation Errors in MKPs
key | value
---------- | ---
date | 2024-05-10T12:36:10+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This Werk affects users, which have installed an MKP with an unloadable `ValueSpec` definition.
During the update process this `ValueSpec` will be loaded in order to apply an update to the
corresponding rulesets. Previously, any error would cause the `RuleSet` UpdateAction to fail.
With this Werk, the faulty `Ruleset` is skipped. Moreover, while `Verifying Checkmk
configuration` the user is prompted with the error and can safely abort the update.
This change also affects the rulesets shipped with Checkmk. However, in case a ruleset fails in this
way, please report the error. This way we can address the error in the ruleset itself.
[//]: # (werk v2)
# Top list dashlet: Introduce best effort querying
key | value
---------- | ---
date | 2024-05-06T08:09:18+00:00
version | 2.4.0b1
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
In some rare cases, the top list dashlet does not display all available metrics
due to limitations in the metric system of Checkmk.
An example of this issue can be observed when using the `CPU utilization`
metric. When using Windows and Linux hosts at the same time, the services of
these hosts conflict with each other, potentially resulting in incomplete
results.
Now the top list dashlet will try to query all available metrics on a best
effort basis if the results are incomplete. If some metrics are still missing,
the dashlet displays an error message with the conflicting metrics.
This information can be used to identify the conflicting services and exclude
them by adding more filters to the dashlet.
[//]: # (werk v2)
# Licensing: Start trial period when switching to CCE or CME
key | value
---------- | ---
date | 2024-05-06T15:10:03+00:00
version | 2.4.0b1
class | feature
edition | cme
component | wato
level | 1
compatible | yes
When updating to an edition with mandatory licensing (CCE and CME), we want to give users enough time to apply the license when updating.
A CME updated to 2.3 will now start in 30-day trial period instead of directly entering the "free" license state if it otherwise would not be licensed.
However, in a distributed setup it is recommended to make use of the change in [werk #16193](https://checkmk.com/werk/16193) to apply the license before the update.
[//]: # (werk v2)
# Missing piggybacked hosts
key | value
---------- | ---
date | 2024-05-10T09:28:11+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a regression in Checkmk 2.3.0 and 2.3.0p1.
Piggybacked hosts containing invalid characters where dropped silently.
This restores the original behavior: Invalid characters in host names are replaced by "_".
Title: "This page was not found." error after operations on pagetypes
Class: fix
Compatible: compat
Component: multisite
Date: 1715326150
Edition: cre
Level: 1
Version: 2.2.0p27
When performing certain operations, such as cloning, deleting, etc., on pagetypes
(views, dashboards, etc.) and when the "Find on this page ..." filter is active
on the page an error "This page was not found" was displayed on the page.
This issue has been resolved and the correct page is now displayed.
Title: Handle nfs mount dirs with whitespace
Class: fix
Compatible: compat
Component: checks
Date: 1715000622
Edition: cre
Level: 1
Version: 2.2.0p27
This werk may affect you, in case you've been monitoring nfs and your mount directory had whitespaces included.
The result would have been a nfs mount service which is always in state <tt>hanging</tt>.
[//]: # (werk v2)
# Handle nfs mount dirs with whitespace
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-05-06T13:03:42+00:00
level | 1
class | fix
component | checks
edition | cre
This werk may affect you, in case you've been monitoring nfs and your mount directory had whitespaces included.
The result would have been a nfs mount service which is always in state <tt>hanging</tt>.
[//]: # (werk v2)
# "This page was not found." error after operations on pagetypes
key | value
---------- | ---
date | 2024-05-10T07:29:10+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
When performing certain operations, such as cloning, deleting, etc., on pagetypes
(views, dashboards, etc.) and when the "Find on this page ..." filter is active
on the page an error "This page was not found" was displayed on the page.
This issue has been resolved and the correct page is now displayed.