Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulnerability Detector module is enabled at the start of the stress test #22565

Closed
MARCOSD4 opened this issue Mar 15, 2024 · 1 comment
Closed
Labels
level/task qa_known Issues that are already known by the QA team type/bug Something isn't working

Comments

@MARCOSD4
Copy link
Member

MARCOSD4 commented Mar 15, 2024

Wazuh version Component Install type Install method Platform
4.8.0-beta4 Wazuh component Manager Packages CentOS

During the testing in Release 4.8.0 - Beta 4 - Footprint Metrics - ALL (2.5d) some warnings related to the vulnerability scanner module have been encountered. After checking the configuration, the vulnerability detection module is disabled but in manager logs we see this module is enabled for a few minutes:

2024/03/12 17:33:10 wazuh-modulesd:vulnerability-scanner: INFO: Starting vulnerability_scanner module.
...
2024/03/12 17:36:19 wazuh-modulesd:vulnerability-scanner: INFO: Vulnerability scanner module is disabled

This happens because at the beginning of the test, it is taking a default Wazuh configuration from a template, which is producing these logs and warnings at the start of the test.

It significantly impacts the results of the stress tests.

@MARCOSD4 MARCOSD4 added type/bug Something isn't working level/task labels Mar 15, 2024
@MARCOSD4 MARCOSD4 changed the title Vulnerability Detector module is enabled during stress test Vulnerability Detector module is enabled at the start of the stress test Mar 15, 2024
@juliamagan juliamagan added the qa_known Issues that are already known by the QA team label Mar 19, 2024
@rauldpm
Copy link
Member

rauldpm commented Mar 20, 2024

From Release testing to Very high impact bugs

This fix will affect the stress test results, we should consider moving it to 4.9.0 instead of 4.8.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task qa_known Issues that are already known by the QA team type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants