Werk #22363: Proxmox VE VM Info: Fix update failure for rules created in 2.4.0
| Component | Checks & agents | ||||
| Title | Proxmox VE VM Info: Fix update failure for rules created in 2.4.0 | ||||
| Date | Sep 23, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Previously, the update from 2.4.0 to 2.5.0 could not validate rules of the
ruleset Proxmox VE VM Info. cmk-update-config showed this warning and
created a crash report:
Exception in ruleset implementation detected (Ruleset: checkgroup_parameters:proxmox_ve_vm_info, ...) Validation errors: [ValidationMessage(location=['lock_duration'], message='Required field missing', ...)]
You then had to fix the rule by hand.
The cause: Checkmk 2.5.0 added the required option Lock duration levels to this ruleset. Rules created in 2.4.0 do not have this option.
The update now adds Lock duration levels with the default values to these
rules: WARN at 15 minutes and CRIT at 30 minutes. The check already used
these levels for these rules, so your monitoring results do not change.
Rules that you did not fix yet are migrated on the next update.