GitLab Runner registration token changed by itself

Summary

Our CI/CD stopped working recently because the tokens no longer matched. Not sure if this is related to gitlab-org/gitlab-ce#4235.

Steps to reproduce

I honestly don't know - I just came back from a few days of vacation and apparently our CI/CD has not been working (it used to work pretty well).

The first error message I got was this:

ERROR: Preparation failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (executor_docker.go:968:0s)

I was able to fix this by running sudo systemctl start docker - I also used sudo systemctl enable docker to automatically start the daemon whenever the server is rebooted.

However our CI/CD still doesn't work - I now get a different error:

Fetching changes...
remote: You are not allowed to download code from this project. fatal: unable to access 'http://gitlab-ci-token:[MASKED]@domain.com/group/project.git/': The requested URL returned error: 403

So I was investigating this one and it turns out that the registration token has apparently changed without us having to manually reset it?

What is the current bug behavior?

The registration token found on http://domain.com/group/project/settings/ci_cd is different from the token that is shown when I ran gitlab-runner list on the terminal.

What is the expected correct behavior?

The two tokens must match (our CI/CD has been working since we started using GitLab - more than 2 years ago).

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:         RedHatEnterpriseServer 7.6
Current User:   git
Using RVM:      no
Ruby Version:   2.5.3p105
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.2
Redis Version:  3.2.12
Git Version:    2.21.0
Sidekiq Version:5.2.7
Go Version:     unknown

GitLab information
Version:        11.11.3
Revision:       e3eeb779d72
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     9.6.11
URL:            http://domain.com
HTTP Clone URL: http://domain.com/some-group/some-project.git
SSH Clone URL:  git@domain.com:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        9.1.0
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 9.1.0 ? ... OK (9.1.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
2/1 ... yes
4/7 ... yes
4/11 ... yes
3/13 ... yes
13/14 ... yes
4/15 ... yes
4/16 ... yes
13/17 ... yes
13/18 ... yes
3/20 ... yes
3/21 ... yes
5/22 ... yes
4/25 ... yes
3/28 ... yes
4/29 ... yes
4/30 ... yes
3/32 ... yes
3/33 ... yes
5/34 ... yes
3/35 ... yes
15/36 ... yes
18/37 ... yes
4/39 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.5.3)
Git version >= 2.21.0 ? ... yes (2.21.0)
Git user has default SSH configuration? ... yes
Active users: ... 9

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished
Edited by Patrick Gregorio