-
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
Investigate the error in the agent_files_deletion
test
#2282
Comments
Issue updateWhile looking for the root cause of this issue, it was seen that several problems take place in this test. In the first run, we can see that everything goes smooth:
Before this first execution, we were able to check that the
After this first execution, if we run the test again we will face the following trouble:
We will solve this problem by adding a However, another problem was encountered here. The error shown below seems to be appearing whenever we run the test and do not have any agent reporting to the
This error is solved by setting another
|
Issue update
The results can be found here. |
Issue updateChecking if the information was in the wazuh-qa/tests/system/provisioning/basic_cluster/roles/master-role/tasks/main.yml Lines 31 to 36 in a2871a6
wazuh-qa/tests/system/provisioning/basic_cluster/roles/master-role/tasks/main.yml Lines 112 to 125 in a2871a6
These changes are present in both master and worker files as is checked in both of them. The file Also, this change was introduced in order to not end the test until the agent is restarted and active: wazuh-qa/tests/system/test_cluster/test_agent_files_deletion/test_agent_files_deletion.py Lines 43 to 46 in 3cdf73a
Lastly, in the Ansible tasks, we set the I will leave here the test results:
The results can be found here. |
While running the system test for the 4.3 release, it was noticed that this test was failing half of the time it was runned:
It seems that it is failing when checking whether there is any information about a particular agent in the
global.db
so this is probably because the manager did not had time enough to register it into the database.The text was updated successfully, but these errors were encountered: