Secondary node exposes the "external_url" of the Primary node in the clone dialog.
Summary
On GitLab 15.1, we started to enable Geo proxying for secondary sites even if the external_url is different on the Primary and Secondary node.
However, it seems that one of the side-effects here is that the Secondary node exposes the URL of the Primary node when clocking the Clone dialog.
Steps to reproduce
- Configure GitLab Geo (15.1 or newer)
- Go to the Secondary node.
- Click the Clone button on one of the projects.
What is the current bug behavior?
URL of the Primary node is shown when trying to clone from the Secondary node.
What is the expected correct behavior?
URL of the Secondary node is shown when trying to clone from the Secondary node.
Relevant logs and/or screenshots
On this screenshot, http://10.66.181.201 is the URL for my secondary node. If you look at clone dialog, it shows http://10.66.181.154/root/agent-configs.git, which is the URL for my primary node.
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)