Skip to content

Fix geo detect site correctly URI

Ben Prescott_ requested to merge bprescott/20221103-geositedetect into master

What does this MR do and why?

The rake task generates the output:

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 "z".
  Or you could set this machine's Geo node name to match the name of an existing database record: "x", "y"
  For more information see:
  doc/administration/geo/replication/troubleshooting.md#can-geo-detect-the-current-node-correctly

The path for the documentation is problematic for two reasons.

  1. can-geo-detect-the-current-node-correctly got changed to can-geo-detect-the-current-site-correctly
  2. It's a source code reference. The file is specified as .md and not .html and /doc/ doesn't work on either GitLab.com or customers' self-managed help pages

I think this needs improving further to link to one of the following

  • https://docs.gitlab.com/ee/administration/geo/replication/troubleshooting.html
  • #{external_url}/help/administration/geo/replication/troubleshooting.html

Don't know what is preferred, or exactly how to achieve the second one.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Ben Prescott_

Merge request reports