-
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
Playbook clean.yaml failed #5641
Comments
Update statusAnalyzing the playbook that fails, executing some tests, and capturing logs. |
Update reportWork continued on this issue in parallel with the v4.9.0-beta2 release, taking advantage of the release tests, to test the modifications on the Test full agents with playbooks modifications 🟢
|
Working on the new bug added to the issue about Central Componentes clean up error |
Update reportThe error with the cleanup of the VMs of the central components tests is due to a bad configuration in the input yaml set. For example, in the yaml used in the Deployability test, in the issue The variable that contains all the definitions of all the VMS is used. The correct thing to do is to use the variable defined as tag Execution with the correction to the input yaml:
|
Central components examples fixed in #5615 |
The issue is reopened as the error appears again in the following issue: wazuh/wazuh#25497 YAML
Logs: |
Closed again, we will open a new issue instead of reopening a closed issue with a PR already merged |
Description
Almost all DTT tests show the following error when executing the clean.yaml playbook:
This playbook does not affect the tests, it is only used to clean the VM after finishing the test.
It is necessary to analyze whether it is necessary to continue using said playbook, since after the JobFlow ends the VM is deleted.
If necessary, this error must be fixed.
Another bug needs to be fixed:
Error:
Fix the Centra Coponents clean up task
The text was updated successfully, but these errors were encountered: