-
Notifications
You must be signed in to change notification settings - Fork 301
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
Scale test is failing #831
Comments
Thanks for catching this. Saw a bunch of quota exceeded error from the logs (the latest run): https://storage.googleapis.com/kubernetes-jenkins/logs/ci-ingress-gce-e2e-scale/1164061805203427328/artifacts/e2e-a8e3dd9eae-886f8-master/glbc.log
|
Well, seems like we leaked exactly one SSL cert, so the last LB creation (for ing-scale-99) was not successful:
Deleting the leaked cert but will look more why it was leaked. |
Requested a quota bump on the project for relevant resources to allow some headroom as well. |
Found the deletion error (in used by) on that leaked SSL cert:
Probably a bug with the GC procedure? As target proxy should be cleaned up prior to SSL cert? |
Okay, test is now passing; https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-ingress-gce-e2e-scale/1164243519703879680 I tend to believe the resource were leaked from an aborted run (which we can't avoid), and the above deletion error came from janitor a day after that. It failed due to some ordering issue in janitor (deleting cert before target proxy), which kubernetes/test-infra#14021 is fixing. |
Ref: https://k8s-testgrid.appspot.com/sig-network-ingress-gce-e2e#ingress-gce-e2e-scale
@MrHohn can you take a look?
The text was updated successfully, but these errors were encountered: