System basic_environment tests fail in 4.8.0-beta4

[Rebits]

Description

During Release 4.8.0 - Beta 4 - System tests it has been detected unexpected errors
in the Basic Environment environment tests test_agent_auth and test_enrollment

• test_agent_auth:

The expected log was not found during the test

E                   TimeoutError: Did not found the expected callback in wazuh-agent1: .*Requesting a key from server: 172\.24\.27\.2

However we can see that it is present in the agent log file:

2024/03/13 18:20:48 agent-auth: INFO: Requesting a key from server: 172.24.27.2

Further research is required

• test_enrollment

Expected log was not found during the test

E                   TimeoutError: Did not found the expected callback in wazuh-agent1: .*Requesting a key from server: 172.24.27.2

However we can see that it is present in the agent log file:

2024/03/13 19:03:33 wazuh-agentd[44457] enrollment_op.c:129 at w_enrollment_request_key(): INFO: Requesting a key from server: 172.24.27.2

Further research is required

• Test case:

  • test_agent_auth[manager_ipv4_agent_ipv4-ipv4-yes]
  • test_agent_auth[manager_ipv4_agent_ipv4-dns-no]
  • test_agent_auth[manager_ipv6_agent_ipv6-dns-yes]
  • test_agent_auth[manager_both_agent_ipv4-dns-no]
  • test_agent_auth[manager_ipv4_agent_both-ipv4-yes]
  • test_agent_enrollment[manager_both_agent_both-ipv4-no]
  • test_agent_enrollment[manager_both_agent_both-ipv6-yes]
  • test_agent_enrollment[manager_both_agent_both-dns-yes]
  • test_agent_enrollment[manager_ipv4_agent_ipv4-ipv4-no]

• Report: basic_env.zip

[juliamagan]

As in other iterations, the log does appear. The problem is in the HostMonitor, which does not work as expected in virtualized environments. We can do an analysis and refactor of this method, or wait for the migration of the system tests.

In the meantime, it is proposed to mark the issue as qa_known, and when the system tests fail it, before opening an issue directly, check the environment logs.

[juliamagan]

After the meeting with @davidjiglesias and @rauldpm, we are going to close this issue as not planned, and the system tests will be launched locally if necessary until we can migrate these tests to the new framework.