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

Remove some Wazuh cluster variables #766

Closed
Selutario opened this issue May 10, 2022 · 3 comments · May be fixed by #868
Closed

Remove some Wazuh cluster variables #766

Selutario opened this issue May 10, 2022 · 3 comments · May be fixed by #868
Assignees
Labels

Comments

@Selutario
Copy link
Member

Selutario commented May 10, 2022

Epic Docu issue
wazuh/wazuh#7108 wazuh/wazuh-documentation#5215

Description

It is intended to make the Wazuh cluster enabled and running by default. This development will be done in:

As a consequence, certain configuration options will disappear. How each option will be affected can be seen in wazuh/wazuh#13351 and wazuh/wazuh#13353. As a summary, the main changes are these:

It will be necessary to update or remove in the Ansible module those variables that are affected:

cluster:
disable: 'no'
node_name: '{{ ansible_hostname }}'
node_type: "{{ 'master' if ansible_hostname == 'wazuh-mgr01' else 'worker' }}"
nodes: '{{ manager_addresses }}'
hidden: 'no'

There are more places with references to these variables, so it will be necessary to search and change all of them and check that the module works correctly after that.

@teddytpc1
Copy link
Member

The changes were tested with 4.4. It failed because some removed parameters are required for that version, but the playbook succeeds until it tries to start the Wazuh manager.

The PR is ready for review and the automatic tests will fail because there are no 4.5.0 packages in pre-release.

@alberpilot
Copy link
Contributor

This issue goes to blocked due to the main development delay.

@teddytpc1 teddytpc1 added the level/task Subtask issue label Apr 26, 2023
@teddytpc1
Copy link
Member

This will be handled as part of the 5.0.0 release changes.

@teddytpc1 teddytpc1 closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants