Skip to content

[BUG] Error install Wazuh-agent with playbook security.yaml #1092

@omiazek-ads

Description

@omiazek-ads

Environment:
Delivery tag:
Platform: OPS Orange Cloud
Configuration:

Traceability:
N/A

Current Behavior:
The playbook security.yaml fails with an error during the TASK [security/wazuh : Join Wazuh Manager]

Expected Behavior:
The playbook security.yaml completes without error

Steps To Reproduce:
Steps to reproduce the behavior:

  1. Create a new node with the playbook cluster.yaml
  2. Run the playbook cluster.yaml with the config tag
  3. Run the playbook security.yaml

Test execution artefacts (i.e. logs, screenshots…)

TASK [security/wazuh : Join Wazuh Manager] ***********************************************************************************
FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true})

Whenever possible, first analysis of the root cause
For an unknown reason, the playbook installs the wazuh-agent v4.9, which is incompatible with our wazuh-manager 4.7.5-1.

Workaround

Edit file in rs-infrastructure:

vi ./roles/security/wazuh/tasks/role-agent.yaml

Add the version 4.7.5-1 here:

  • name: install wazuh agent
    apt:
    name: wazuh-agent=4.7.5-1
    state: present
    update_cache: yes
    cache_valid_time: 86400

Bug Generic Definition of Ready (DoR)

  • The affect version in which the bug has been found is mentioned
  • The context and environment of the bug is detailed
  • The description of the bug is clear and unambiguous
  • The procedure (steps) to reproduce the bug is clearly detailed
  • The tested User Story / features is linked to the bug if available
  • Logs are attached if available
  • A data set attached if available

Bug Generic Definition of Done (DoD)

  • the modification implemented (the solution to fix the bug) is described in the bug.
  • Unit tests & Continuous integration performed - Test results available - Structural Test coverage reported by SONAR
  • Code committed in GIT with right tag or Analysis/Trade Off documentation up-to-date in reference-system-documentation repository
  • Code is compliant with coding rules (SONAR Report as evidence)
  • Acceptance criteria of the related User story are checked and Passed

Metadata

Metadata

Assignees

No one assigned

    Labels

    CCBIssue for CCBbugSomething isn't workingopsTicket from ADS operation team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions