-
Notifications
You must be signed in to change notification settings - Fork 30
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
Not all agents get disconnected in test_shutdown_message
#5199
Comments
After talking to @TomasTurina, it was found that when the agent stops it sends |
By monitoring the logs and the agent statuses, we have been able to see that the test started when there were agents that were not yet |
On hold due to Beta 6 testing |
With the proposed solution, the test passes without problem when launched individually, but when all tests in the environment are launched it fails. We are checking if the environment is dirty from the previous tests, but these tests take 1:40h, which makes it very slow to debug. |
Finally, it was found that the environment was dirty and was not registered in the expected manager. It remains to upload the results of the complete test set to ensure that it does not fail. |
Description
During the system tests launched for 4.8.0 Beta 5 at wazuh/wazuh#22824, it has been found that not all agents go offline:
This test has been modified recently, so we should check if the waiting time for the check is as expected, because if it is, even if no errors appear in the managers, it could indicate some kind of performance error. After all, after several executions, the error seems consistent.
The text was updated successfully, but these errors were encountered: