Weird results when filtering by runner description string

Error 1: Inconsistent results in the Admin Area > Runners View

The default count of runners is inaccurate.

Steps to reproduce

  • Navigate to Admin Area > Runners
  • Observe that the count of runners is incorrect.

Screen_Shot_2022-10-24_at_6.57.28_PM

Error 2: New runner in view when applying filter

When using GitLab 15.5, if I filter by a string to filter down runners by a runner description, I sometimes gain another runner. I'm not sure if that runner is supposed to be there initially, but it seems to only appear when I clear the filters. This seems to happen in general, even when I register a new runner, it doesn't always appear in the list unless I refresh multiple times.

runner-bug

Steps to reproduce

  1. Filter by runner description
  2. Clear filters

  1. Register a new runner
  2. Refresh
  3. Refresh again

Example Project

What is the current bug behavior?

I'm not seeing the correct number of runners at all times.

What is the expected correct behavior?

I should see all runners in the all tab.

Relevant logs and/or screenshots

runner-bug

Output of checks

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 Darren Eastman