You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier today we started observing workflows were queuing, but the self-hosted runners were not picking them up.
After some try/error/restart, I ended up in a state where:
no runner are being executed in the self-hosted infra (GCP)
the controller is asking github "is there a runner I need to wait for?"
github says yes, and the self-hosted runner page shows 1 runner.
Hence, it seems like there is a 'zombie' runner, which doesn't exists on the infra (VM instance count is zero), but exists from the Github point of view.
Clicking 'delete' runner on the github interface shows a 'Sorry, there was a problem deleting your runner'.
Is there a way to debug/force-delete runners on the github side?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
Earlier today we started observing workflows were queuing, but the self-hosted runners were not picking them up.
After some try/error/restart, I ended up in a state where:
Hence, it seems like there is a 'zombie' runner, which doesn't exists on the infra (VM instance count is zero), but exists from the Github point of view.
Clicking 'delete' runner on the github interface shows a 'Sorry, there was a problem deleting your runner'.
Is there a way to debug/force-delete runners on the github side?
Beta Was this translation helpful? Give feedback.
All reactions