Werk #22416: Clustered services are only disabled by rules matching the cluster
| Component | Checks & agents | ||
| Title | Clustered services are only disabled by rules matching the cluster | ||
| Date | Oct 5, 2026 | ||
| Level | Prominent Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
This affects users who map services from a node to a cluster with the rule Clustered services and disable some of them with Disabled services or Disabled checks.
A clustered service belongs to the cluster, so the cluster's rules decide whether it is disabled. Service discovery and monitoring did not consistently follow this:
- On the service discovery page of the node, a disabled clustered service was listed under Disabled services with bulk actions, instead of under Disabled clustered services - located on cluster host. Enabling it from there reported success but had no effect.
- On the service discovery page of the cluster, the service was shown as vanished or not at all if the rule also matched the node.
- A rule matching only the node disabled the service on the cluster, while both service discovery pages showed it as monitored.
Now a Disabled services or Disabled checks rule disables a clustered service only if it matches the cluster. The node lists the service under Disabled clustered services - located on cluster host, and the cluster lists it under Disabled services, where it can be enabled again. Like other disabled services (see werk #19806), disabled clustered services are no longer written to the autochecks file of the node.
This restores the behaviour introduced by werk #7128, which was lost in Checkmk 2.0.
Incompatibility: a rule matching only the node no longer has any effect on a clustered service. If you have disabled clustered services with such a rule, they are monitored on the cluster after the update. To keep them disabled, make the rule match the cluster.