Runner creation gets stuck (due to missing created runner data)

Summary

Runner creation gets stuck.

Original from Slack link: https://gitlab.slack.com/archives/CETG54GQ0/p1685704954940079

Example Project

https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist

What is the current bug behavior?

I’ve been trying to setup a new Runner, but the button keeps spinning forever, even though the GraphQL call returns almost immediately.

image

The GraphQL call returns immediately with the following response, but the UI doesn’t update.

{"data":{"runnerCreate":{"runner":null,"errors":[],"__typename":"RunnerCreatePayload"}}}

Logs show no reason for runners to be failing 🤔 https://log.gprd.gitlab.net/goto/8e6846b0-013f-11ee-8afc-c9851e4645c0

What is the expected correct behavior?

The browser navigates to the registration page to continue the registration.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

Edited by Miguel Rincon