A secondary node fails to identify itself with relative URLs
Steps to reproduce
I changed "external_url" from http://sizov-secondary-geo.gogitlab.ml
to http://sizov-secondary-geo.gogitlab.ml/gitlab/
I edited the node to match the change
I ran reconfigure
Problem
Regardless of the slash, in the end, the node won't identify itself as a secondary.
What is the expected correct behavior?
I expect it to identify itself
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.6.6p146 Gem Version: 2.7.10 Bundler Version:1.17.3 Rake Version: 12.3.3 Redis Version: 5.0.9 Git Version: 2.27.0 Sidekiq Version:5.2.9 Go Version: unknown GitLab information Version: 13.2.0-pre Revision: 089631428f0 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 11.7 URL: http://sizov-secondary-geo.gogitlab.ml/gitlab HTTP Clone URL: http://sizov-secondary-geo.gogitlab.ml/gitlab/some-group/some-project.git SSH Clone URL: git@sizov-secondary-geo.gogitlab.ml:some-group/some-project.git Elasticsearch: no Geo: yes Geo node: Undefined Using LDAP: no Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 13.3.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 >= 13.3.0 ? ... OK (13.3.0) 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 ... 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? ... skipped (no tmp uploads folder yet) 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: ... 1/1 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.6) Git version >= 2.22.0 ? ... yes (2.27.0) Git user has default SSH configuration? ... yes Active users: ... 1 Is authorized keys file accessible? ... skipped (authorized keys not enabled) GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 6.x - 7.x? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking Geo ...
GitLab Geo secondary database is correctly configured ... not a secondary node Database replication enabled? ... not a secondary node Database replication working? ... not a secondary node GitLab Geo tracking database is configured to use Foreign Data Wrapper? ... not a secondary node GitLab Geo tracking database Foreign Data Wrapper schema is up-to-date? ... not a secondary node GitLab Geo HTTP(S) connectivity ... not a secondary node GitLab Geo is available ... yes GitLab Geo is enabled ... yes This machine's Geo node name matches a database record ... no Try fixing it: You could add or update a Geo node database record, setting the name to match this machine's Geo node name "http://sizov-secondary-geo.gogitlab.ml/gitlab/". Or you could set this machine's Geo node name to match the name of an existing database record: "http://sizov-primary-geo.gogitlab.ml/", "http://sizov-secondary-geo.gogitlab.ml/gitlab/" For more information see: doc/administration/geo/replication/troubleshooting.md#can-geo-detect-the-current-node-correctly HTTP/HTTPS repository cloning is enabled ... yes Machine clock is synchronized ... yes Git user has default SSH configuration? ... yes OpenSSH configured to use AuthorizedKeysCommand ... yes GitLab configured to disable writing to authorized_keys file ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes
Checking Geo ... Finished
Checking GitLab subtasks ... Finished