Check_MK 2.0.0p15(CEE) - Automatic Agent update problem

Troubleshooting
1

Hi,
after upgrade from 1.6p23 CEE to 2.0.0p15 CEE agent update won’t work as expected.
Agent deployment was (and is supposed to) activated by a host tag “t_autoClientUpdate” which worked perfectly in 1.6
Now the plugin is installed with the agent, but refuses to update:

Agent Bakery: Agent Updates are disabled for hostname myhost because it is not listed in the explicit list of host names.

The Check_MK agent check shows en error about a non-signed agent.

image
image915×26 8.37 KB

Only when I put the host’s name explicitly into the rule, it works:

image
image692×58 4.13 KB

Is this a bug or a feature?
Target Server is Windows Server 2019 btw…

2

Check these settings in your setup, you probably applied a filter there:

image
image632×615 68 KB

3

Hi,
is that CEE? Because mine (CEE) looks different…

image
image804×660 78.9 KB

Anyway, I think, it’s a problem with the updater plugin, because agent bakery works for the tagged hosts

4

Yes, they are both CEE, but you are in the ‘Global Settings’, I was referring to the ‘Agent Bakery’. See the breadcrumbs in the top of my screenshot.

5

Sorry, need my eyesight checked…
image
image
image
How are these conditions combined? “AND” or “OR” ?
I was under the impression it’s “OR” e.g. tag match OR host name match

6

No, like in most cases in Checkmk this is a ‘AND situation’.
This place is not intended to control agent updates on a daily basis, this place is for testing and major rollouts.
For daily business I suggest you stick to your host tags, that is best practice. But rather than using the global settings you want to update you agent update rule with the tag. So systems that do not do automatic updates do not even receive the plugin.

7

I deleted the host names and it worked.So I got it wrong all the time…

That’s what I had in mind. I was only confused by “AND” vs. “OR”. Explicit host names were meant for testing.
Thank you for clearing that up for me.

1 Like
8

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.