Free on-demand webinars: Learn how to set up, configure, and get more out of Checkmk – Pick your webinar

Werk #22212: Systemd discovery rejects empty conditions again

Component Checks & agents
Title Systemd discovery rejects empty conditions again
Date Nov 17, 2026
Level Trivial Change
Class Bug Fix
Compatibility Incompatible - Manual interaction might be required
Checkmk versions & editions
3.0.0b1
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

Werk #13124 made the discovery rule sets refuse empty conditions: Restrict by description or Restrict by name without any entry, an entry with an empty pattern, or Restrict by state without any state. At some point this validation stopped working, so such rules could be saved again. Setup refuses them again now.

Existing rules with empty conditions keep working as before and are not changed by the update. An empty list of conditions still means "no restriction", and an empty pattern still matches the way it did. If you have such a rule, the configuration check of cmk-update-config reports it as an invalid rule configuration and asks whether to continue. Open the rule in Setup afterwards and untick the empty condition or enter a pattern; the affected fields are marked.

The systemd rule sets Systemd single service discovery, Systemd single socket discovery, Systemd single service, Systemd single socket, Systemd services summary and Systemd sockets summary now use the current rule set API.

The deprecated rule sets Systemd single services discovery and Systemd single services are removed. They have had no effect since werk #14781 replaced them, and the update deletes their remaining rules.

To the list of all Werks