[//]: # (werk v2)
# Allow filesystem service rule levels to go above 100%
key | value
---------- | ---
date | 2024-06-25T10:07:14+00:00
version | 2.3.0p9
class | feature
edition | cre
component | wato
level | 1
compatible | yes
Previously, the option `Levels for used/free space` of various
`Filesystem` rules did not allow percent values beyond 101.0 %. With
this werk any non-negative value can be set, allowing virtualized file
systems to be monitored more granularly.
[//]: # (werk v2)
# Fix float rule values not checking all validations
key | value
---------- | ---
date | 2024-06-25T07:08:34+00:00
version | 2.3.0p9
class | fix
edition | cre
component | wato
level | 1
compatible | no
In Checkmk, it's possible for any rule value to specify custom
validation functions to stop users from accidentally entering invalid
data. Before this werk, the set of rule fields that allowed floating
point values to be set in rare cases did not check these custom
validation functions when setting up a rule.
With this werk, we restore the expected functionality and check
the validity of all floating point values in a rule.
**Incompatibility**
Some users might have created rules which should not have been valid.
You will find out if such a rule is present in your setup when you
update your site. The update process will raise an error warning you of
any rule values that break custom validators. This error will tell you
about the invalid rule and the reason it is invalid. Please abort the
update process, fix the invalid value and restart the update process.
**Plugin developers**
If you have created a rule value with the `validate` (ValueSpec) or
`custom_validate` (Form Spec) argument set, your rule will now correctly
use provided functions to check the validity of the data. No change to
the rule is necessary.
[//]: # (werk v2)
# notification_rules: typo in field sort_order_for_bulk_notifications
key | value
---------- | ---
date | 2024-07-03T05:22:21+00:00
version | 2.3.0p9
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
The REST-API endpoints previously had a typo in the field
'sort_order_for_bulk_notifications'. The second t was missing.
This werk now corrects this.
[//]: # (werk v2)
# Event Console fix regex match in rule text
key | value
---------- | ---
date | 2024-07-01T15:31:04+00:00
version | 2.3.0p9
class | fix
edition | cee
component | ec
level | 1
compatible | yes
Event console method compile_matching_value had a typo
which caused a valid regex to not match, because it was sent as a string
SUP-19224
[//]: # (werk v2)
# TrippLite UPS: discover devices with .1.3.6.1.4.1.850.1 as sysObjectID
key | value
---------- | ---
date | 2024-06-26T16:13:34+00:00
version | 2.3.0p9
class | feature
edition | cre
component | checks
level | 1
compatible | yes
TrippLite UPSs use OID .1.3.6.1.4.1.850.1 as sysObjectID.
These devices are currently not discovered and monitored.
This has now been changed and they will be discovered.
Werk 16431 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# omd restore: Fix RuntimeError: Failed to determine site version
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-06-11T12:03:43+00:00
level | 1
class | fix
component | omd
edition | cre
Due to a regression introduced by <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the
command `omd restore <NEW_SITE> <ARCHIVE_PATH>` could fail:
```
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/main.py", line 3522, in _restore_backup_from_tar
old_site.replacements(),
^^^^^^^^^^^^^^^^^^^^^^^
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/contexts.py", line 136, in replacements
raise RuntimeError("Failed to determine site version")
```
The failure only occured, if the user provided a site name, which differed from the original name,
and the original site did no longer exist. This crash also affected the `Migrate existing Site`
function of the appliance.
If you are affected by this crash, but are unable to update, then you can start be restoring the
site without a new name. The site can then be renamed with `omd mv`.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# omd restore: Fix RuntimeError: Failed to determine site version
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-06-11T12:03:43+00:00
level | 1
class | fix
component | omd
edition | cre
- Due to a regression introduced by Werk <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the
? -----
+ Due to a regression introduced by <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the
command `omd restore <NEW_SITE> <ARCHIVE_PATH>` could fail:
```
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/main.py", line 3522, in _restore_backup_from_tar
old_site.replacements(),
^^^^^^^^^^^^^^^^^^^^^^^
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/contexts.py", line 136, in replacements
raise RuntimeError("Failed to determine site version")
```
The failure only occured, if the user provided a site name, which differed from the original name,
and the original site did no longer exist. This crash also affected the `Migrate existing Site`
function of the appliance.
If you are affected by this crash, but are unable to update, then you can start be restoring the
site without a new name. The site can then be renamed with `omd mv`.
+
[//]: # (werk v2)
# parent_scan: resolve failing parent scan background job
key | value
---------- | ---
date | 2024-07-02T12:39:27+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
The REST API endpoint to initiate the parent scan background job
returned a 204 status code, which theoretically is correct. However,
the started background job failed immediately due to an invalid Python
syntax concerning the involving requested hosts. This werk fixes the issue.
[//]: # (werk v2)
# kube_pod_conditions: Support PodReadyToStartContainers Condition
key | value
---------- | ---
date | 2024-07-01T14:21:43+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
As of Kubernetes version 1.28, the PodCondition `PodHasNetwork` was renamed to
`PodReadyToStartContainers`. With this Werk, both naming conventions are supported.
This Werk also tweaks the summary of the check to be more consistent across different
Kubernetes environments.
[//]: # (werk v2)
# Transfer Arista temperature sensors to our common entity sensor monitoring
key | value
---------- | ---
date | 2024-06-28T13:27:10+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | no
The existing entity sensor check plug-in discovers temperature, fan and binary
power sensors. The Arista check plug-in only covered temperature sensors and
used the common ENTITY-MIB.
Please run a re-discovery on the affected Arista devices. If there are rules
configured for the Arista temperature sensor services then these might have to
be adapted because the Arista check plug-in used the entPhysicalDescr entries
for the service items and the entity sensor check plug-in uses the
entPhysicalName entries.