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

Test cluster connection in Reliability Test is not detecting the correct pattern #4364

Closed
pro-akim opened this issue Jul 25, 2023 · 1 comment
Assignees
Labels

Comments

@pro-akim
Copy link
Member

Description

Workload benchmark testing were performed for Release of v4.6.0-pre-alpha1
Running manually reliability/test_cluster/test_cluster_logs/test_cluster_connection/test_cluster_connection.py::test_cluster_connection over artifacts created by workload benchmark pipeline (It should be fixed #4299) it is possible to find that the cluster_connection test is not finding the correct pattern in cluster log releasing the following message:

Failed: Could not find "Sucessfully connected to master" message in the worker_21

However, checking manually the logs, it could be checked that the message was in the worker_21's cluster.log

2023/07/25 09:27:01 INFO: [Worker CLUSTER-Workload_benchmarks_metrics_B274_manager_21] [Main] Successfully connected to master.

Current behavior

Error message:

Failed: Could not find "Sucessfully connected to master" message in the worker_21

Expected behavior

Finding the log and passing the test without error messages.

@pro-akim
Copy link
Member Author

pro-akim commented Aug 2, 2023

Update

Different results were obtained re - running the test over the artifacts.
Related to
#4386

Issue closed

@pro-akim pro-akim closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2023
@wazuhci wazuhci moved this from In progress to Done in Release 4.6.0 Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants