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
[Flaky test] [release-1.20] pull-kubernetes-e2e-gce-100-performance failing on Prometheus stack timeout #98039
Comments
@ehashman: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig testing just guessing, I haven't looked into the test failure in detail |
/sig release |
/kind failing-test |
|
cc: @kubernetes/sig-scalability @kubernetes/release-engineering |
@jkaniuk - can you please take a look into it? |
/assign @jkaniuk |
Which jobs are flaking:
pull-kubernetes-e2e-gce-100-performance
Seems to only be on the release-1.20 branch?
Which test(s) are flaking:
e2e.go: ClusterLoaderV2
Testgrid link:
https://testgrid.k8s.io/presubmits-kubernetes-scalability#pull-kubernetes-e2e-gce-100-performance
Reason for failure:
Further investigation shows the Prometheus stack is timing out:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/97998/pull-kubernetes-e2e-gce-100-performance/1349479663537229824/#1:build-log.txt%3A1783
more log excerpt
Anything else we need to know:
The text was updated successfully, but these errors were encountered: