Re-register an agent about wazuh-ansible HOT 5 OPEN

Hi,

It is the expected behavior: the agent will be registered only the first time that Ansible runs.

We should research how to re-register an agent explicitly.

from wazuh-ansible.

This would help with an issue I see frequently, where agents get duplicate IDs from the manager during registration, so only one of them is truly registered and they all think they have been registered with the same ID.

from wazuh-ansible.

@coryrwagner Are the agents in front of a load balancer?

from wazuh-ansible.

Running this play on a wide infrastructure, I thought something like this can help solve the problem:

- name: Wazuh | Check if client.keys exists
  stat: path=/var/ossec/etc/client.keys
  register: check_keys

But for wazuh agent v3.9.0, whenever you run this task over a machine with an already connected agent, a new agent with the same name pops-up.
Is this issue still open?

from wazuh-ansible.

Hi,

Since Wazuh 4.0 version, there is a new feature called auto-enrollment which solves this issue. The agent and manager are continuously checking connectivity between them. In case you deregister an agent, after a few seconds the agent will lose the connection
with the manager and after the agent will try to reconnect:

SG

from wazuh-ansible.