pipeline jobs stuck without global runner
I noticed in a fresh installation of gitlab (gitlab/gitlab-ce:latest) that a ci/cd pipeline get's stack if no global runner is available.
What do I mean with no global runner? If one registers a project or group specific runner, but the admin did not register a global runner, the job gets still stuck, as if no runner would be available.
There seam to be an error when verifying if a runner is available or not, so the job does not get scheduled to the available runner and that runner therefore does not pick up that job (api returns 204 no content).
Edited by Klaus Frank