Impossible to add/remove Geo Nodes when primary is not configured properly
Customer ran into this today. The FQDN did not match the hostname (e.g. foobar.domain.com vs foobar), and so the Geo Node status panel prevented us from updating the UI:
We mucked with the console before realizing that we could update external_url to the FQDN and ran gitlab-ctl set-geo-primary-node.
Would a better way be to see if we have write access to the DB?