-
Notifications
You must be signed in to change notification settings - Fork 1.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
Bug: Failed to check if runner is busy
#183
Comments
@callum-tait-pbx I think this has been disappeared in my env once I've added |
Currently deployed with a PAT which doesn't have a |
Just deployed again using 0.11.2 with the github app auth configuration at the organisation level. I still get the error (see below. I can confirm permission wise my app has: Repo Permissions
Org Permissions
2020-11-13T13:01:03.904Z ERROR controllers.Runner Failed to check if runner is busy {"runner": "sre-actions-runner-system/sre-actions-runners-runner-deployment-k2j7j-ctpbz", "error": "runner not found"} Again my runner seems to actually have deployed but it would be good to figure out why this error happens and fix whatever is causing it. |
same issue for me. log: 2020-11-27T15:17:21.506Z ERROR controllers.Runner Failed to unregister runner {"runner": "default/self-hosted-1x-deployment-dfgwp-hbc7d", "error": "runner is busy"} I'm using the runner for my organization. My app permissions:
Actions-runner-controller
Container Setting
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I no longer get this on the controller v0.18.0, I'm not sure when we stopped getting the error, this was probably fixed at some point by accident. If this is an issue for someone on this thread still, upgrade your controller to latest. If you still get the error raise a new issue and link to this one to provide addiitonal context. |
This has been mentioned in a few places, I think it would be good to have an issue raised specifically for this going forward.
Steps to Reproduce
config
kubectl logs controller-manager-777fb76ddb-4tjpz -c manager
Error
Behaviour
This doesn't appear to prevent the runner being created nor scaling from working however there is a problem somewhere as we shouldn't be getting errors thrown at all
Example Runner Yaml
The text was updated successfully, but these errors were encountered: