Checkmk werks level1 July 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
398 discussions

[2.3.0] Checkmk Werk 17119 created: parent_scan: resolve failing parent scan background job

by Checkmk werks level 1

[//]: # (werk v2) # parent_scan: resolve failing parent scan background job key | value ---------- | --- date | 2024-07-02T12:39:27+00:00 version | 2.3.0p9 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.

2 months, 2 weeks

[2.3.0] Checkmk Werk 16864 created: snmp: Fix error in SNMP context serialization introduced with werk 16862

by Checkmk werks level 1

[//]: # (werk v2) # snmp: Fix error in SNMP context serialization introduced with werk 16862 key | value ---------- | --- date | 2024-07-03T07:48:10+00:00 version | 2.3.0p9 class | fix edition | cre component | checks level | 1 compatible | yes Werk 16862, which solved one SNMP context serialization bug, introduced another one. When using SNMP contexts, the change activation crashes in 2.3.0p8. After this Werk, SNMP contexts should work without errors.

2 months, 2 weeks

[2.3.0] Checkmk Werk 17077 created: Allow filesystem service rule levels to go above 100%

by Checkmk werks level 1

[//]: # (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.

2 months, 2 weeks

[2.3.0] Checkmk Werk 17076 created: Fix float rule values not checking all validations

by Checkmk werks level 1

[//]: # (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.

2 months, 2 weeks

[2.3.0] Checkmk Werk 17016 created: notification_rules: typo in field sort_order_for_bulk_notifications

by Checkmk werks level 1

[//]: # (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.

2 months, 2 weeks

[2.3.0] Checkmk Werk 16533 created: Event Console fix regex match in rule text

by Checkmk werks level 1

[//]: # (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

2 months, 2 weeks

[2.3.0] Checkmk Werk 17031 created: TrippLite UPS: discover devices with .1.3.6.1.4.1.850.1 as sysObjectID

by Checkmk werks level 1

[//]: # (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.

2 months, 2 weeks

[2.4.0] Checkmk Werk 16243 created: Cease to provide builds for ubuntu-20.04, Debian-10 and SLES12sp5

by Checkmk werks level 1

[//]: # (werk v2) # Cease to provide builds for ubuntu-20.04, Debian-10 and SLES12sp5 key | value ---------- | --- date | 2024-05-02T11:54:35+00:00 version | 2.4.0b1 class | fix edition | cre component | omd level | 1 compatible | yes

2 months, 2 weeks

[2.4.0] Checkmk Werk 16431 adapted: omd restore: Fix RuntimeError: Failed to determine site version

by Checkmk werks level 1

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`. +

2 months, 2 weeks

[2.4.0] Checkmk Werk 17119 created: parent_scan: resolve failing parent scan background job

by Checkmk werks level 1

[//]: # (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.

2 months, 2 weeks

← Newer
1
...
32
33
34
35
36
37
38
39
40
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 July 2024