Release 4.3.7 - Release Candidate 1 - Integration tests

[jmv74211]

Description

Wazuh QA: Branch	Wazuh QA: Commit	Wazuh: Tag	Wazuh: Commit
4.3/master	40715db	v4.3.7-rc1	wazuh/wazuh@7df62c1

We are going to check that the integration tests of the 4.3 and master branch of wazuh-qa work correctly using the 4.3.7-rc1 version of wazuh.

The tests will be performed both in the local environment and in Jenkins using CentOS as the manager OS. As for the agents, Linux, Windows and macOS will be used as required.

Tests Integration - Status

Main RC issue

• Release 4.3.7 - Release Candidate 1 wazuh#14562

Previous RC analysis

• None. This is the first.

References

Color	Status
🟢	All tests passed successfully
🟡	All tests passed but there are some warnings
🔴	Some tests have failures or errors
🔵	Test execution in progress
⚫	To Do
🟠	Jenkins provision fails
🟣	All skipped

Test Integration - Results

Name	Jenkins
OS	Linux		Windows	Solaris	macOS
Target	Manager	Agent	Agent	Agent	Agent
active_response	🟢	🟢	🟡	NA	NA
agentd	NA	🟢	🟢	NA	NA
analysisd	🟢	NA	NA	NA	NA
api	🟡	NA	NA	NA	NA
authd	🟢	NA	NA	NA	NA
enrollment	NA	🟢	🟡	NA	NA
fim	🟢	🟢	🟡	🟢	🟢
gcloud	🟢	NA	NA	NA	NA
github	🟢	🟢	NA	NA	NA
logcollector	🟢	🟢	🟡	🟢	🟢
logtest	🟢	NA	NA	NA	NA
office365	🟢	🟢	NA	NA	NA
remoted	🟢	NA	NA	NA	NA
rids	🟢	NA	NA	NA	NA
rootcheck	🟢	NA	NA	NA	NA
vulnerability_detector	🟢	NA	NA	NA	NA
wazuh_db	🟢	NA	NA	NA	NA

[jmv74211]

While running the integration tests for the 4.3.7-rc1 release using the 4.3 branch of wazuh-qa, a problem was detected related to agentd on Windows. The same test has been rerun for several times and all other times it has passed successfully.

Round 1	Round 2	Round 3	Round 4	Round 5
🔴	🟢	🟢	🟢	🟢

The reported problem is the following

AssertionError: Expected message Requesting a key from server: testServer1 never arrived! Stage: 0, message number: 0

=========================== short test summary info ===========================
FAILED test_agentd/test_agentd_multi_server.py::test_agentd_multi_server[server_down_fallback_tcp]
======= 1 failed, 27 passed, 6 skipped, 1 warning in 2241.80s (0:37:21) =======

The same behavior has also been observed in the 4.4 branch, where this test has also failed

Round 1	Round 2	Round 3
🔴	🔴	🟢

AssertionError: Expected message 'Requesting a key from server: testServer1' never arrived! Stage: 1, message number: 1

=========================== short test summary info ===========================
FAILED test_agentd/test_agentd_multi_server.py::test_agentd_multi_server[server_down_fallback_tcp]
======= 1 failed, 27 passed, 6 skipped, 1 warning in 2222.02s (0:37:02) =======

It is necessary to ensure that for the case where the integration test has failed in Windows, the product is working correctly and that it is a false positive test. For this, it will be necessary to test it manually and attach the necessary tests. This has been proposed in this issue

This issue has also been opened to investigate the corresponding integration test and to apply the necessary fix in case the false positive test is confirmed.

Until we confirm that it is a false positive and that the Windows agent is working correctly, this issue will be blocked.

[jmv74211]

In this issue it has been proven that the detected agentd bug was a false positive, so everything is correct 🟢 .