Pipelines fail on 18.1

Nobody has claimed this yet.

When a pipeline runs now it errors with this:

RuntimeError (CI job token signing key is not set):
  /home/git/gitlab/lib/ci/job_token/jwt.rb:82:in `key'
  /home/git/gitlab/lib/ci/job_token/jwt.rb:41:in `decode'
  /home/git/gitlab/app/finders/ci/auth_job_finder.rb:34:in `find_job_by_token'
  /home/git/gitlab/app/finders/ci/auth_job_finder.rb:15:in `execute!'
  /home/git/gitlab/lib/api/ci/helpers/runner.rb:155:in `job_from_token'
  /home/git/gitlab/gems/gitlab-utils/lib/gitlab/utils/strong_memoize.rb:138:in `bind_call'
  /home/git/gitlab/gems/gitlab-utils/lib/gitlab/utils/strong_memoize.rb:138:in `block (2 levels) in do_strong_memoize'
  /home/git/gitlab/gems/gitlab-utils/lib/gitlab/utils/strong_memoize.rb:34:in `strong_memoize'
  /home/git/gitlab/gems/gitlab-utils/lib/gitlab/utils/strong_memoize.rb:137:in `block in do_strong_memoize'
  /home/git/gitlab/lib/api/ci/helpers/runner.rb:82:in `authenticate_job!'
  /home/git/gitlab/lib/api/ci/runner.rb:276:in `block (2 levels) in <class:Runner>'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:58:in `call'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:58:in `block (2 levels) in generate_api_method'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.5.1/lib/active_support/notifications.rb:208:in `instrument'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:57:in `block in generate_api_method'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:328:in `execute'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:260:in `block in run'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.5.1/lib/active_support/notifications.rb:208:in `instrument'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:240:in `run'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/endpoint.rb:316:in `block in build_stack'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:36:in `call!'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:29:in `call'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:36:in `call!'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:29:in `call'
  /home/git/gitlab/lib/gitlab/middleware/ip_address.rb:14:in `block in call'
  /home/git/gitlab/lib/gitlab/ip_address_state.rb:11:in `with'
  /home/git/gitlab/lib/gitlab/middleware/ip_address.rb:13:in `call'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:36:in `call!'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:29:in `call'
  /home/git/gitlab/vendor/bundle/ruby/3.2.0/gems/grape-2.0.0/lib/grape/middleware/base.rb:36:in `call!'

Is there an environment variable that is needed?

I tried:

GITLAB_CI_JWT_SIGNING_KEY_FILE=/secrets/ci_jwt_signing_key.pem

But still fails.

Start with lib/ci/job_token/jwt.rb:82 and the Docker environment configuration for the CI job token signing key. Reproduce the pipeline failure on GitLab 18.1 and trace the configured key path through runner authentication. Done means pipelines authenticate successfully without the signing-key runtime error.

Written by the indexing model from the issue text.

Description

Contributor guide

First steps

Research direction

Assessment