500 error when fetching runner list in admin page due to `upgradeStatus`
Summary
Incident: gitlab-com/gl-infra/production#7437 (closed)
I am seeing a 500 error when fetching runners with upgradeStatus on https://staging.gitlab.com/.
Steps to reproduce
I have found 2 ways to reproduce this bug on of which is user-facing:
In Admin -> Runners
Visit https://staging.gitlab.com/admin/runners to load the runners list, the runners cannot be loaded.
Use a GraphQL query
Visit https://staging.gitlab.com/-/graphql-explorer
use the following query
query getRunners { runners { nodes { id upgradeStatus __typename } __typename } }
Example Project
What is the current bug behavior?
The query fails with a 500 error
What is the expected correct behavior?
Data is loaded
Output of checks
(it very likely this happens in Gitlab.com, but admins would be able to reproduce this at the moment)
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)