Error on new Runner token workflow registration (k8s)

How to Use GitLab
,
1

Hello everyone
We are running GitLab CE on Version 16.11.7 on Kubernetes right now.

Problem to solve

We use the GitLab runners on Kubernetes too. Since we have to move to the new Token Workflow to upgrade to Version 17 we tried to move to the workflow, but we always get the same error:

FATAL: Runner configuration other than name and executor configuration is reserved (specifically --locked, --access-level, --run-untagged, --maximum-timeout, --paused, --tag-list, and --maintenance-note) and cannot be specified when registering with a runner authentication token. This configuration is specified on the GitLab server. Please try again without specifying any of those arguments. For more information, see https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html#changes-to-the-gitlab-runner-register-command-syntax

The interesting part here, we have neither of the values mentioned defined in the config.

Steps to reproduce

Right now we tried the following things:

  • Generated New Runner Token
  • Deleted Token Secret and Deployment and re-deployed with Helm
  • Removed Runner Configuration → all default
  • Fresh GitLab installation

Even after the new installation the issue was still there.

Versions

Versions

  • GitLab 16.11.7

Conclusion

Is this a known issue or did someone have a similar problem to solve?
Thank you very much for your inputs!

2

Hi Dario,

I figured it out. You need to use this in your values file or your CLI:

–set gitlab-runner.runners.locked=null

It’s described here.

And I found the culprit with helm get values --all release_name