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

Tool or job to cleanup ingress related GCP resource after test failure #483

Closed
MrHohn opened this issue Sep 19, 2018 · 10 comments
Closed

Tool or job to cleanup ingress related GCP resource after test failure #483

MrHohn opened this issue Sep 19, 2018 · 10 comments

Comments

@MrHohn
Copy link
Member

MrHohn commented Sep 19, 2018

Ref #438 (comment). Ingress scale test occasionally will hit quota issue due to resource leaked by previous runs / test failures. Test failures can be caused by various reasons --- new change breaks controller (e.g. nil pointer), test timeout, test infrastructure problem (e.g. run#858 never finish), etc.

Manually deleting leftover resource every time is not tenable. We should at least have a cleanup script we can run. More preferable if an automated job can run it.

@krzyzacy Is this something we should put on https://k8s-testgrid.appspot.com/sig-testing-misc#ci-janitor? Or we should have our own janitor because this is ingress specific?

@krzyzacy
Copy link
Member

if you can fit into the current janitor script, sure :-)

@MrHohn
Copy link
Member Author

MrHohn commented Sep 19, 2018

Humm, https://github.com/kubernetes/test-infra/blob/master/boskos/janitor/janitor.py does include most of the ingress related resource, except SSL cert.

Though I'm not seeing it runs against ingress test projects; https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/maintenance-ci-janitor/584

We should probably enable it?

@MrHohn
Copy link
Member Author

MrHohn commented Sep 19, 2018

In fact, seems like ingress-project is included:
https://github.com/kubernetes/test-infra/blob/795cceb4ce411fa43933fb6534c208a6d470e1ab/boskos/janitor/deployment.yaml#L52

Though we don't put the ingress scale project under that category. I can create a new category "ingress-scale-project" and add it to the same place.

@krzyzacy
Copy link
Member

krzyzacy commented Sep 19, 2018

oh, that's handled by boskos, not ci-janitor

(also ci-janitor is borked 🙃 fixing with kubernetes/test-infra#9486)

@krzyzacy
Copy link
Member

it's handled by https://github.com/kubernetes/test-infra/blob/master/boskos/janitor/janitor.go

if you have access to k8s-prow you can check logs there, which project you are looking for?

@MrHohn
Copy link
Member Author

MrHohn commented Sep 19, 2018

@krzyzacy Thanks for the quick response, I were looking for k8s-ingress-e2e-scale-backup, which is not defined in any bosko resource yet.

BTW did you mean https://prow.k8s.io? Not actually sure which job to look at :)

@krzyzacy
Copy link
Member

I mean https://pantheon.corp.google.com/home/dashboard?project=k8s-prow

if it's not in the pool then it will be handled by ci-janitor - let's wait for next run.

@MrHohn
Copy link
Member Author

MrHohn commented Sep 20, 2018

if it's not in the pool then it will be handled by ci-janitor - let's wait for next run.

Thanks! Will check on the next run. And unfortunately I don't have access to k8s-prow :/

@krzyzacy
Copy link
Member

time="2018-09-20T04:48:12Z" level=info msg="Will clean up k8s-ingress-e2e-scale-backup with ttl 24 h" 
time="2018-09-20T04:48:38Z" level=info msg="successfully cleaned up project k8s-ingress-e2e-scale-backup" 

it should be cleaned up, double check the project? if something is still lingering then we should add them to the janitor script.

@MrHohn
Copy link
Member Author

MrHohn commented Sep 20, 2018

@krzyzacy Awesome, yeah seems like it should work. Good to know this is already covered :)

Closing this issue. I will send follow up to cleanup SSL cert as well.

@MrHohn MrHohn closed this as completed Sep 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants