-
Notifications
You must be signed in to change notification settings - Fork 53
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
After a couple of hours of not using the runner, it will become offline #556
Comments
Hello? |
What does the logs of the pod say? I am no longer working with tietoevry, and no longer have write-access to the repo - but might be able to shed some light on what is wrong. |
we have these in our logs of the pod
looks like it can't be removed which cause it crashloop since the same pod is already running, do know where to look why it's failing to do so?
|
Then there is already a runner registered with this name in the GH console, force-remove those. It's maybe wise to set the pod-policy to restart: Never - then they won't reappear and end in this state. |
BTW: Love traktor ;-) |
I think this is the problem that we need to always force-remove it and sometimes recreate the runner-pool, I've added
|
@davidkarlsen just wanted to confirm that we don't see any issues since one week, looks like it helped, thank you! |
@davidkarlsen it happened again, even with the In the meantime, until a fix is found I unded up setting a cron that runs every day inside kubernetes to delete the pod. This way a new one is spawned and is automatically registered in github.
|
So after everything is up an running, did run some jobs, all is good but then, after not using the runner for some hours, it wil become offline, and I will have to delete the runner pool and delete the runner from github so that it gets recreated. Is there some setting like idle timeout or something like that? I do have the minimum runner set to 1 in my CRD
The text was updated successfully, but these errors were encountered: