-
Notifications
You must be signed in to change notification settings - Fork 1k
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
The deprecated runner version fails after job assignment not after start to listen for jobs #3366
Comments
I am facing the same issue, how come the image is deprecated? it was released just last month. Are we supposed to update them every now and then? |
There are lot of discussions on this topic. I used to version deprecation within a month But the runner was failing before picking a job, so the job was waiting in the queued state for 24 hours. We were able to provision a new runner with the new version. But with the latest version, the runner started to fail after picking a job, so it causes job failure. |
Hi @enescakir thanks for raising this. Do you have a link to a failed run you could share? |
@luketomlinson It's the run which I previously shared logs. |
@luketomlinson The interesting part is that not all jobs are failing. We use different GitHub Apps for local development, and they manage to run jobs with this older version. However, the production GitHub app can't run with this version. I don't know its details but the GitHub backend might have a certain check for the assigned job, and it may have determined that this job can't run with this runner version. |
Thanks @enescakir, that's all helpful info, I'm looking into it. |
Got same problem today. We have 3 runner scale sets in one namespace, with same docker image, but they target different repositories. And only one fails with this error:
|
This issue should be fixed now. Old runners should no longer be able to be assigned jobs. @enescakir @MuhammadElsaeed @dt-napier Can you confirm you're no longer seeing this? |
Thanks to your prompt solution, @luketomlinson, it's back to functioning as it used to. Was this problem related to the backend services?
|
Hey @enescakir, yep it was a backend issue. I'm going to close this out for now, but please open an issue if you see it again! |
Hi, I am facing the same issue @luketomlinson |
Upgrade to 2.317.0 is ok. |
Describe the bug
In the previous versions, the runner used to fail prior to the job assignment and kept the job as queued if the runner version is deprecated. However, in the latest version, the failure occurs after the job has been picked, resulting in an immediate job failure. Waiting in queue for a runner with the new version was a better option.
To Reproduce
Assign a job to runner with version
2.316.1
Expected behavior
Exit the runner due to deprecation before picking a job
Example log from older versions
The text was updated successfully, but these errors were encountered: