Skip to content

Only migrate the tracking database when in a secondary site

Douglas Barbosa Alexandre requested to merge migrate-geo-database-only-on-secondary into main

What does this merge request do and why?

The changes in !3387 (merged) break an existing Geo development setup with a tracking database enabled on a primary site. This MR only migrates the tracking database when in a secondary site.

Installing gitlab-org/gitlab Ruby gems
--------------------------------------------------------------------------------
Bundle check passed.

--------------------------------------------------------------------------------
Processing gitlab rails and Geo DB migrations
--------------------------------------------------------------------------------
rake aborted!
Don't know how to build task 'db:migrate:geo' (See the list of available tasks with `rake --tasks`)
Did you mean?  db:migrate:redo
               db:migrate
               db:migrate:down
               db:migrate:up
               db:migrate:ci
               db:migrate:reset
               db:migrate:main
/Users/dbalexandre/.asdf/installs/ruby/3.1.4/bin/bundle:25:in `load'
/Users/dbalexandre/.asdf/installs/ruby/3.1.4/bin/bundle:25:in `<main>'
(See full trace by running task with --trace)
❌️ ERROR: 'asdf exec bundle exec rake db:migrate db:test:prepare db:migrate:geo db:test:prepare:geo' failed.

Merge request checklist

  • This change is backward compatible. If not, please include steps to communicate to our users.
  • Tests added for new functionality. If not, please raise an issue to follow-up.
  • Documentation added/updated, if needed.
  • Announcement added, if change is notable.
  • gdk doctor test added, if needed.
  • Add the ~highlight label if this MR should be included in the CHANGELOG.md.

Merge request reports