Werk #22170: A failing bakery plug-in no longer affects other hosts
| Component | Agent bakery | ||
| Title | A failing bakery plug-in no longer affects other hosts | ||
| Date | Nov 10, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
A bakery plug-in that failed for one host caused two problems for all other hosts. An agent file that a rule references, but that is missing on the site, had the same effects.
The page Windows, Linux, Solaris, AIX highlights the buttons Bake agents and Bake and sign agents when agent packages need baking. With a failing plug-in, the page could not determine this for any host. The buttons then stayed unhighlighted, as if all agent packages were up to date. Nothing on the page pointed to the failure.
The bake itself stopped at the failing host. Hosts that came later in
the bake got no new agent packages, although their configuration was
valid. This also hit the bakes of the global setting Automatically
create monitoring agents. Their errors only appear in
~/var/log/web.log.
Now the page highlights the buttons in these cases as well. A warning above the agent list names the affected hosts and folders, together with the error message. If several plug-ins fail for a host, the warning names each of them. If the check on the page fails for another reason, the page still highlights the buttons.
The bake creates the packages of all other hosts. It still ends with an error that names the affected hosts, and these hosts keep their previous agent package. Such a bake now also removes the packages of hosts that no longer exist.