GitLab Runner receives 404 checking for jobs

GitLab CI/CD
1

Problem to solve

When GitLab Runner 17.11 polls for jobs, the GitLab API endpoint returns a 404. This began after upgrading to 17.11.

May 15 03:30:32 git2 gitlab-runner[702]: WARNING: Checking for jobs... failed                runner=**** status=POST https://****/api/v4/jobs/request: 404 Not Found (404 Not found)
May 15 03:30:40 git2 gitlab-runner[702]: WARNING: Checking for jobs... failed                runner=**** status=POST https://****/api/v4/jobs/request: 404 Not Found (404 Not found)
May 15 03:30:48 git2 gitlab-runner[702]: WARNING: Checking for jobs... failed                runner=**** status=POST https://****/api/v4/jobs/request: 404 Not Found (404 Not found)
May 15 03:31:32 git2 gitlab-runner[702]: WARNING: Checking for jobs... failed                runner=**** status=POST https://****/api/v4/jobs/request: 404 Not Found (404 Not found)

Steps to reproduce

GitLab Runner 17.11 makes POST requests to /api/v4/jobs/request, but the endpoint consistently returns a 404.

Configuration

?

Versions

Please select whether options apply, and add the version information.

  • Self-managed
  • GitLab.com SaaS
  • Dedicated
  • Self-hosted Runners

Versions

  • GitLab: v17.11.2-ee
  • GitLab Runner: 17.11.1
1 Like
2

No idea why, but you need to create new tokens. See Runner not picking up jobs after upgrade to 17.11

3

Thanks!

4

Thanks for reporting. See Runner not picking up jobs after upgrade to 17.11 (#543351) · Issues · GitLab.org / GitLab · GitLab for details.

1 Like
5

Please upgrade to GitLab 17.10.7, 17.11.3, or 18.0.1 to fix this issue: GitLab Patch Release: 18.0.1, 17.11.3, 17.10.7 | GitLab

2 Likes