-
Notifications
You must be signed in to change notification settings - Fork 55
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
Kruize remote monitoring functional failures due to 502 from listRecommendations #1281
Comments
Commented out test_list_recommendations_cpu_mem_optimised test that failed with 502 error and running the sanity testsuite manually, all the tests passed now. Will run the entire testsuite and check again. |
I see an error occurring while creating the experiment. It could be related to the state, such as whether Kruize and its related pods, including the database service, are ready to handle the request. |
Yes, that create experiment issue failed due to 502 error in this job, hence commented the below test & other tests work fine. We need to check why 502 occurs when we run the entire sanity bucket. |
Two new tests failed now, after commenting the above test and running the entire functional testsuite manually, due to 502 error response from list recommendations:
|
Executed the test suite again the above 2 failures are not seen, 502 error issue seems to be intermittent
These 43 failures are due to known issues. Executed only the sanity bucket by enabling the skipped test - test_list_recommendations_cpu_mem_optimised test, it passed, didn't see the 502 error.
|
Logs of another sanity run that failed with kruize pod restart |
I have run one of the failing tests alone with the below builds, here are the results: pytest -s test_list_recommendations.py::test_list_recommendations_cpu_mem_optimised --cluster_type openshift Executed this test 5 times: With 0.0.22_mvp, did not see the failure (could be very intermittent though I did not see the failure in 5 runs) Note: When the test fails kruize pod is restarted @msvinaykumar @khansaad - Can you please take a look at this issue. |
Issue is seen on 0.0.25_mvp build too. |
Describe the bug
Kruize remote monitoring functional tests are failing with different issues on openshift with latest kruize 0.0.24_mvp image
https://ci.app-svc-perf.corp.redhat.com/job/ExternalTeams/job/Autotune/job/kruize_release_tests/139/ - Kruize scalelab
https://ci.app-svc-perf.corp.redhat.com/job/ExternalTeams/job/Autotune/job/kruize_functional_tests/128/ - kruize scalelab
https://ci.app-svc-perf.corp.redhat.com/job/ExternalTeams/job/Autotune/job/kruize_functional_tests/128/testReport/junit/rest_apis/test_list_recommendations/test_list_recommendations_profile_notifications_cpu_zero_test_1_True_update_metrics0_323002_CPU_usage_is_zero__No_CPU_Recommendations_can_be_generated_/
https://ci.app-svc-perf.corp.redhat.com/job/ExternalTeams/job/Autotune/job/kruize_functional_tests/128/testReport/junit/rest_apis/test_list_recommendations/test_list_recommendations_cpu_mem_optimised/
The text was updated successfully, but these errors were encountered: