Runner locked to nothing after registering with a token not tied to a group or project
Summary
We power down GitLab and the Runner Docker containers outside of business hours. When a new Runner is launched each morning, it is registered automatically with GitLab using a registration token not tied to any particular project or group. The Runner's (surprising) new default behaviour of starting locked means that the runner will be locked to nothing and so it will never pick up a job.
Steps to reproduce
- Launch GitLab with a pre-set token not tied to a project or group.
- Use this token to register a fresh Runner.
- Runner will start locked to nothing and will never pick up jobs.
Expected behavior
Runner starts not-locked or locked to all groups or fails to start with a fatal error.
Environment description
Shared Runners v10+ running against a private GitLab instance. Both applications being run in Docker containers
Used GitLab Runner version
10.0.0+