GENERIC agent missing from baked agent list

[nir (Niklas Rehberger)]

CMK version: CEE 2.1.0p19
OS version: Ubuntu 20.04

Hello Everyone,

we are currently trying to figure out why our agent bakery is not creating the GENERIC agent. I can see the “Vanilla” one. I checked related issues in the forum but could not quite find an answer that fits our case.
These are the topics I checked:

Agent Bakery erstellt keinen "Generic" Agent

Guten Tag, wir fangen gerade mit unserem Monitoring neu an aufzubauen. Haben die Checkmk Enterprise 1.6.0p16 im Einsatz. Wenn wir den Agent für das Autoupdate vorbereiten mit der entsprechenden Regel, wird nach dem wir die Änderungen aktiviert haben und die Backery erfolgreich abgeschlossen haben, kein “Generic Agent” erstellt. Prüfen wir “Automatic agent updates” ist die Konfiguration mit dem grünen Hacke versehen???

Agent bakery dummy client with updater, how to do?

Hallo, what is the right way to build a dummy agent for the bakery to use as first generic target via curl/ wget to pull the individual package in the next step? Configuring a host for every os and insert the update plugin? Thanks Ralf

Agent bakery: Is it possible to add features to the VANILLA agent?

Hello, up to now I’ve tried to keep the number of different agents in the bakery as small as possible. Essentially I’ve created all agent rules in the root folder. Unfortuntely this is not possible any more. The number of agents is growing. Now it’s not easy to find the correct agent to download when somebody other than me intends to add a new host. So the question is: is it possible to modify the VANILLA agent to add the agent updater feature? So it would be possible to always install this a…

What I gathered is that rules without any parameters that are present in the Main folder get added to the Generic agent. We have many rules located inside the Main folder.
Could a misplaced/misconfigured rule stop the Bakery from creating the Generic agent?

Thankful for all insights

nir

[aeckstein (Andre Eckstein)]

Hi,
maybe the setting - Bake agent packages - Do not bake a generic agent package for this folder.** (Default value) is set on the main directory and is inherited down the folders ?

[nir (Niklas Rehberger)]

This is the only setting I can find on the Main folder. So it’s explicitly told to bake the generic agent. I’m pretty sure this setting is set as default, we did not change this by hand.

[aeckstein (Andre Eckstein)]

And this is also set and inherited on the subfolders where the hosts reside, where you want the agent to be created ?

[nir (Niklas Rehberger)]

All subfolder settings regarding the baking rule look like this (default)

I’m not 100% sure how to interpret this.

The main reason we were looking for the generic agent is to have a default one to install on new systems, that then pulls the right version via cmk-update-agent, the Vanilla agent obviously does not have the agent updater plugin available.

[aeckstein (Andre Eckstein)]

So its actively disabled on that folder.

You don´t need to use a generic package, every package with the correct agent updater configuration will work, as the agent updater will automatically update itself after the first installation when the installed agent hash does not match the one from the bakery for that particular host.

[nir (Niklas Rehberger)]

If any package that has the updater configured will work, that’ll do for our case!
Thanks!