Skip to content

Inaccurate check: GitLab Geo tracking database is correctly configured ... no

Summary

I got this rake gitlab:geo:check failure:

GitLab Geo tracking database is correctly configured ... no
  Try fixing it:
  Check the tracking database configuration as the connection could not be established
  For more information see:
  http://127.0.0.1:3001/help/administration/geo/setup/database.md

But it was inaccurate. The Geo tracking database is correctly configured, and the Rails application is able to use the connection.

So this check is broken.

Steps to reproduce

  1. Install GDK + Geo gitlab-development-kit!4780 (merged)
  2. Run rake gitlab:geo:check
  3. Notice GitLab Geo tracking database is correctly configured ... no
  4. The GDKs are actually working and Geo is syncing things

Example Project

What is the current bug behavior?

This rake gitlab:geo:check failure happens even if the Geo tracking database connection works:

GitLab Geo tracking database is correctly configured ... no
  Try fixing it:
  Check the tracking database configuration as the connection could not be established
  For more information see:
  http://127.0.0.1:3001/help/administration/geo/setup/database.md

What is the expected correct behavior?

GitLab Geo tracking database is correctly configured ... yes

Relevant logs and/or screenshots

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)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.