Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the filebeat_node_name variable assignment for the wazuh-production-ready playbook #1384

Closed
2 tasks
YisDav opened this issue Aug 20, 2024 · 1 comment · Fixed by #1441 or wazuh/wazuh-documentation#7910
Assignees
Labels

Comments

@YisDav
Copy link
Member

YisDav commented Aug 20, 2024

Description

It was found that the filebeat_node_name variable was only being assigned to the ansible-filebeat-oss role in the wazuh-produciton-ready playbook:

# Wazuh cluster
- hosts: manager
roles:
- role: "../roles/wazuh/ansible-wazuh-manager"
- role: "../roles/wazuh/ansible-filebeat-oss"
filebeat_node_name: node-4

Tasks

  • Fix the variable assignment
  • Test the change and provide evidence
@YisDav YisDav added type/bug level/task Subtask issue labels Aug 20, 2024
@wazuhci wazuhci moved this to Backlog in XDR+SIEM/Release 5.0.0 Aug 20, 2024
@wazuhci wazuhci moved this from Backlog to In progress in XDR+SIEM/Release 5.0.0 Oct 16, 2024
@YisDav YisDav self-assigned this Oct 16, 2024
@YisDav
Copy link
Member Author

YisDav commented Oct 18, 2024

Issue evidence

The issue has been replicated, demonstrating that in the deployment of the Wazuh-distributed environment with ansible, the variable filebeat_node_name is not being correctly assigned. This issue has been traced back to the file playbooks/wazuh-production-ready.yml. However, the documentation contained in file README.md needs also to be updated to match the new playbook configuration.

Original error

image

Solved error

Once the error was identified, the corrections were applied using the new Ansible configuration. Including this configuration, the dashboard is now able to show the detected vulnerabilities.

Configuration file

image

Dashboard vulnerabilities

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment