-
Notifications
You must be signed in to change notification settings - Fork 32
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
Full Yellow Local - WazuhDB tests in 4.2 #1535
Labels
Comments
snaow
changed the title
Full-Green - Fix autoconfiguration in WazuhDB tests in 4.2
Full-Green - WazuhDB tests in 4.2. Autoconfiguration does not work.
Jul 2, 2021
damarisg
changed the title
Full-Green - WazuhDB tests in 4.2. Autoconfiguration does not work.
Full Yellow Local - WazuhDB tests in 4.2. Autoconfiguration does not work.
Jul 5, 2021
It has been detected that this test fails in case of the manager has already registered some agents before the test is run. This should be fixed in other to guarantee independence between tests.
|
snaow
changed the title
Full Yellow Local - WazuhDB tests in 4.2. Autoconfiguration does not work.
Full Yellow Local - WazuhDB tests in 4.2.
Aug 9, 2021
snaow
changed the title
Full Yellow Local - WazuhDB tests in 4.2.
Full Yellow Local - WazuhDB tests in 4.2
Aug 9, 2021
Closed by #1643 |
This was referenced Aug 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This issue is part of the #1516. After the research #1493, it has been detected that
wazuh_db
tests do not properly autoconfigure the testing environment. These tests do not start automaticallywazuh_db
daemon. In an environment where the Wazuh manager has not started for the first time, these tests will fail in some cases.Research results
Pipeline parameters
Packages details
In the case presented in the description, wazuh_db tests fail in the following cases:
The error output obtained is:
All tests should autoconfigure the testing environment in order to prevent unexpected behaviours.
The text was updated successfully, but these errors were encountered: