Werk #20125: Command line core restarts no longer bake agents
| Component | Agent bakery | ||
| Title | Command line core restarts no longer bake agents | ||
| Date | Aug 6, 2026 | ||
| Level | Prominent Change | ||
| Class | New Feature | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
What changed
With the Automatically create monitoring agents setting enabled, cmk -R, cmk -O and cmk -U used to bake agents as part of writing the core configuration.
They no longer do.
Everything that reaches the Agent Bakery through Setup is unchanged: activating changes still bakes agents, and so do auto-discovery and renaming hosts.
What to do
If you rely on a scripted cmk -R or cmk -U to refresh agent packages, bake explicitly instead:
cmk --bake-agents
Why this change
The option's own description says Automatically update agents at Activate changes, and that is what it was meant to do.
Baking from the command line was a side effect of where the feature lived:
it hung off core configuration generation, so every path that wrote a core config -- including a plain cmk -R -- rebuilt agent packages too.
That made a core restart unexpectedly expensive, and it put a Setup feature inside the monitoring core.
The trigger now sits in Setup, where the option's description already promised it was.
Technical background
The global setting Automatically create monitoring agents moves from the core configuration domain to the GUI one.
cmk-update-config relocates the stored value during the update; you do not need to set the option again.
As a side effect, toggling it no longer requires a core configuration regeneration.