[bug] Wrong link url(hostname/admin/runners/id) for gitlab runner, gitlab-ce 14.8.4(docker).

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Start new docker container with latest version(v14.8.4) gitlab-ce image, then login with root account and register a new gitlab runner. While I visit the gitlab runner detail or edit config of gitlab runner, the link of runner name and edit button are wrong.

Steps to reproduce

  1. docker pull gitlab/gitlab-ce # Here latest version is 14.8.4.
  2. docker run -d -p 5443:443 -p 5080:80 -p 5022:22 --name gitlab --restart always -v /usr/share/gitlab/issue/config:/etc/gitlab -v /usr/share/gitlab/issue/logs:/var/log/gitlab -v /usr/share/gitlab/issue/data:/var/opt/gitlab gitlab/gitlab-ce # Here config data and logs are empty folders.
  3. Waiting for starting.
  4. Root login with password in config/initial_root_password.
  5. Select Menu -> Admin -> Runner.
  6. Register gitlab runner with Registration token. # Docker, and register successfully.
  7. Check the link #(hash) and the link of edit button. The links are $(docker hostname)/admin/runners/1 and $(docker hostname)/admin/runners/1/edit. They are wrong. Actually I can visit detail page and edit page correctly with IP:5080/admin/runners/1.

Example Project

Sorry, not provided.

What is the current bug behavior?

Wrong link url. Actually I can reach right page with correct url IP:5080/admin/runners/1/edit.

What is the expected correct behavior?

Visit right page via correct url.

Relevant logs and/or screenshots

When mouse hover on #1 (tCPFwajs) image

Edit is similar to it, but append edit at last.

Output of checks

Sorry, not provided.

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`)


System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.7.5p203
Gem Version:    3.1.4
Bundler Version:2.1.4
Rake Version:   13.0.6
Redis Version:  6.2.6
Sidekiq Version:6.4.0
Go Version:     unknown

GitLab information
Version:        14.8.4
Revision:       ef2df7d848f
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     12.7
URL:            http://29acba12e955
HTTP Clone URL: http://29acba12e955/some-group/some-project.git
SSH Clone URL:  git@29acba12e955:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        13.23.2
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
root@29acba12e955:/#

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)


Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.23.2 ? ... OK (13.23.2)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: 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 (cluster/worker) ... 1/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 ...

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? ... skipped (no tmp uploads folder yet)
Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Projects have namespace: ...
2/1 ... yes
Redis version >= 5.0.0? ... yes
Ruby version >= 2.7.2 ? ... yes (2.7.5)
Git user has default SSH configuration? ... yes
Active users: ... 1
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished
root@29acba12e955:/#

Possible fixes

Sorry, not provided.

Finally, thanks for your reading.

Best regards.

Edited by 🤖 GitLab Bot 🤖