Closed jesusjimsa closed 3 years ago
I am investigating this error and it seems to be in the ManInTheMiddle
class. This class was heavily modified in the pull request that added integration tests for agentd: #768. Some parts were deleted and I suspect that's what causes the error about the wrong protocol. Specifically the part about the class tree:
https://github.com/wazuh/wazuh-qa/blob/2391575ffb08bcc45010fb37ed2cfac20e49b38d/deps/wazuh_testing/wazuh_testing/tools/monitoring.py#L731-L750
I will keep looking for a solution and try to fix this to move on with analysisd tests for Windows registry as described here: #904.
I have finally found the error. In the pull request I mentioned in the previous comment this line was modified: https://github.com/wazuh/wazuh-qa/blob/2391575ffb08bcc45010fb37ed2cfac20e49b38d/deps/wazuh_testing/wazuh_testing/tools/monitoring.py#L596
This is causing that, event when ManInTheMiddle
is configured for UDP, the TCP class is used. Reverting the change fixes the problem and is working.
Description
Analysisd integration tests are failing in Wazuh 4.0.0 due to the change in the protocol used for the connection between the agent and the manager. Current analysisd tests use UDP to connect to the socket, but Wazuh 4.0.0 uses TCP. This needs to be changed to fix these tests.
They are printing this error when they fail now: