Runner 'contacted at' value is empty after runner registration
Summary
Reported in https://gitlab.com/gitlab-com/account-management/western-north-america/google-cloud-gdch/-/issues/18.
A recently-registered runner will show that it has not yet contacted GitLab, even though a new runner manager will be present and shown online.
Steps to reproduce
-
Create a runner
-
Register the runner
-
Go to the runner details. It will show that the runner has not contacted, even though the runner manager shows as online:
Example Project
What is the current bug behavior?
A recently-registered runner will show that it has not yet contacted GitLab, even though a new runner manager will be present and shown online.
What is the expected correct behavior?
I can see two possible behaviors here:
I believe that scenario 2 has fewer downsides than scenario 1.
Relevant logs and/or screenshots
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)