Vulnerability Detection E2E Initial Scan failure

[Rebits]

Descritpion

We've identified a challenge in https:/wazuh/wazuh-jenkins/issues/6246 where several VD tests are failing. This appears to stem from issues outlined in #4938.

Investigation into this matter is imperative, and corrective actions are needed to address the failed tests.

[Rebits]

Development branch
fix-tmp-vd-e2e

---

Build: https://ci.wazuh.info/job/Test_e2e_system/242/

[Rebits]

Opened #5032. Currently testing

[rauldpm]

About errors

• If no new package is installed, no alert will be generated, expected

Failed: Some agents has not been scanned:['agent1', 'agent2'].
Failed: Index state is not consistent with the alerts

• Related to connection issue

2024/02/29 17:19:07 wazuh-authd: WARNING: OS_RecvSecureClusterTCP(): Connection reset by peer
2024/02/29 17:19:08 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:09 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:10 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:11 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:12 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:13 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:14 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:15 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:16 wazuh-authd: WARNING: Could not connect to socket 'queue/cluster/c-internal.sock': Connection refused (111).
2024/02/29 17:19:16 wazuh-authd: ERROR: Could not send message through the cluster after '10' attempts.

E               ConnectionRefusedError: [Errno 111] Connection refused

• We will merge the pull request and we will review those errors in RC1

[rauldpm]

LGTM

[rauldpm]

We will merge the pull request and we will review those errors in RC1

[Rebits]

Initial Scan tests seems to work as expected for Beta 3. Check results in #5081

[rafabailon]

LGTM

[davidjiglesias]

LGTM