Account for seed project in replicate-geo-database
Recently, we added a self-monitoring seed project for fresh GitLab installs (gitlab#208454 (closed)).
replicate-geo-database is run, we check
gitlab_is_active?, which checks whether the primary database exists with a non-empty
projects table. If it detects a
projects table with records, it will raise a warning. Users can pass
--force to the command to proceed even when
Now that there is a seed project, whenever a user runs
replicate-geo-database with a fresh install on the secondary, they will always encounter this message, which could be confusing.
Steps to reproduce
Follow the instructions to set up a single-node Geo primary and secondary instance with Omnibus.
What is the current bug behavior?
replicate-geo-database, it will incorrectly warn the user that data was found inside the database. Yes, there is data, but it is the seeded project.
What is the expected correct behavior?
Replication should be allowed to continue without displaying the warning or exiting the program.