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

Outdated version of https://github.com/actions/runner causes crash loop #706

Closed
1 of 2 tasks
ToMe25 opened this issue Jul 27, 2021 · 7 comments
Closed
1 of 2 tasks

Comments

@ToMe25
Copy link
Contributor

ToMe25 commented Jul 27, 2021

Describe the bug
It seems that after trying to update the runner software the pod gets stuck in an perpetual crash loop.
For some reason it was working earlier today even tho the new release is 6 days old, but that might have been because it didn't restart the pod since then, which got forced by me updating the deployment yaml and reapplying it.
I had something like this earlier with the last update, however there was a runner image update shortly after I encountered the issue which fixed it, so I didn't report it.

Checks

  • My actions-runner-controller version (v0.x.y) does support the feature
  • I'm using an unreleased version of the controller I built from HEAD of the default branch

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a version of the runner with an outdated actions runner version, i guess
  2. try to get it to execute an action
  3. See the error

Expected behavior
I expected the runner pod to either update once and then work or not update at all.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • Controller Version v0.19
  • Deployment Method kubectl
  • Helm Chart Version N/A

Additional context
The log from one of the pods: https://pastebin.com/3m6pxYir

@ToMe25
Copy link
Contributor Author

ToMe25 commented Jul 27, 2021

Somehow this fixed itself now, even tho I tried for hours to get it to work before reporting it without any success.

@ToMe25
Copy link
Contributor Author

ToMe25 commented Jul 27, 2021

I was away for a while and now the problem is back...

@mumoshu
Copy link
Collaborator

mumoshu commented Jul 28, 2021

@ToMe25 Hey! Thanks for reporting, but unfortunately I don't think we can debug this on our end. Have you already reported your issue to actions/runner?

@ToMe25
Copy link
Contributor Author

ToMe25 commented Jul 28, 2021

@mumoshu I have not reported that to them, because last time I had this issue it seemed to me like it was caused by the pod restarting whenever the runner updated.
This time it didn't seem to restart actually, which surprised me, however it still looked like a container related issue to me.
If you think this is an issue with the runner itself, tell me and I will report it to them.

@ToMe25
Copy link
Contributor Author

ToMe25 commented Jul 28, 2021

Uh, I forgot to mention, but while the runners are set to be ephemeral, they don't seem to actually restart after the update.
Last time they did definitively restart after updating, putting them in an endless loop.

@toast-gear
Copy link
Collaborator

Closing this as this as we have an existing issue for solving this problem. If you would like to show your support on actions/runner#485 as the inability to opt-out of this behaviour is in GitHub's hands (please do as it's a bit silly that GitHub offers no solution, especially as it causes lots of issues for anyone running Actions in containers)

@ToMe25
Copy link
Contributor Author

ToMe25 commented Aug 19, 2021

I didn't know there was an issue for this already.
I have reacted to some comments on the runner issue.
Thanks for letting me know.

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

3 participants