-
Notifications
You must be signed in to change notification settings - Fork 48
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
ARC should handle OOM killed runners #143
Comments
Hello! Thank you for filing an issue. The maintainers will triage your issue shortly. In the meantime, please take a look at the troubleshooting guide for bug reports. If this is a feature request, please review our contribution guidelines. |
Moved issue to hooks, since the hook should be responsible for maintaining resources that it creates |
happened here as well |
Hey everyone, The main problem is that we do not use the scheduler to schedule pods. The reason is that we need workflow pods to land on the same machine where the runner is. There is an option to use a kube scheduler, however, it requires the |
I think i am facing different issue I am using arc with dind template as explained in the documentation Instead of getting something useful on the action logs, like returning oom status and i have to force kill the action |
Checks
Controller Version
0.8.0
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
When the runner is OOMKilled, nothing appends and the pod stays in OOMKilled status. The controller doesn't seem to handle this case, and the job finally times out.
Describe the expected behavior
I think ARC should handle the case the runner is OMMKilled by stopping the job in GitHub with an error status.
Additional Context
Controller Logs
Runner Pod Logs
The text was updated successfully, but these errors were encountered: