Describe the bug
It seems that an outdated runner is very able to register. Which it can do in a loop. And then exhaust every available runner registration.
It seems to me that GHA infrastructure should just... not register the invalid runner at all, but I suspect it will be easier to effect change here.
Could the runner find out if it's a supported version and bail before even trying to register if it's too old?
To Reproduce
Steps to reproduce the behavior:
- Run a runner, set it to auto-restart on any failure
- Let it go a bit stale
Expected behavior
GHA to... reject invalid runners rather than register a runner that is, de facto, useless.
Runner Version and Platform
n/a
OS of the machine running the runner? OSX/Windows/Linux/... Linux
What's not working?
n/a
Job Log Output
n/a
Runner and Worker's Diagnostic Logs
n/a
Describe the bug
It seems that an outdated runner is very able to register. Which it can do in a loop. And then exhaust every available runner registration.
It seems to me that GHA infrastructure should just... not register the invalid runner at all, but I suspect it will be easier to effect change here.
Could the runner find out if it's a supported version and bail before even trying to register if it's too old?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
GHA to... reject invalid runners rather than register a runner that is, de facto, useless.
Runner Version and Platform
n/a
OS of the machine running the runner? OSX/Windows/Linux/... Linux
What's not working?
n/a
Job Log Output
n/a
Runner and Worker's Diagnostic Logs
n/a