CMK-380

TitleBakery: New host does not have an agent by default
ComponentAgent Updater & Bakery, Base
Date2018-02-20
StateNew
ClassStory


Als Nutzer der Agent Bakery moechte ich fuer neue Hosts ohne zusaetzlichen Aufwand einen gebackenen Agenten zur Verfuegung haben, damit ich mir einen unnoetigen Arbeitsschritt ersparen kann.   When using the agent bakery, e.g. only with the VANILLA and GENERIC agent and a new host is being added to the monitoring, the bakery does not find an agent for this new host. The "host agent" page is also showing no agent: [http://localhost/heute/check_mk/wato.py?folder=&host=localhost&mode=agent_of_host#] This seems to be caused by the agent_bakery.find_agents_of_host function which assumes that the hosts can be matched explicitly by the stored agent configs. Since the new host was not available during last baking, the host is not listed in the agent configs and no agent is matching. How to solve this? Idea #1: Mark the bakery dirty on new / renamed hosts? Idea #2: Change agent_bakery.find_agents_of_host to match at least the GENERIC agent for these hosts?