Runner registration returning 500 errors

We are seeing 500 errors with runner registrations. We have identified the cause, and are working on a fix.
More details https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984

Work continues for a fix to the identified cause.
More details https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984

A workaround has been identified to register a runner using an authentication token: https://docs.gitlab.com/runner/register/#register-with-a-runner-authentication-token Incident only impacting the deprecated runner registration method.

Work continues to fix the deprecated runner registration method.
More details https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984 Workaround: register runner with an authentication token.

Work to fix the deprecated runner registration method continues. Workaround: register runner with an authentication token.
More details https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984

As a workaround is available (using an authentication token to register a new runner) the status of this incident has been downgraded to 'Partial Service Disruption'

A fix for this problem has been merged into the codebase - it should become available on GitLab.com in the next 6-7 hours.
For more information please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984

The deployment to production has started and we are expecting it to complete in approximately 1 hour. More details https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984