Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
omnibus-gitlab
omnibus-gitlab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 870
    • Issues 870
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 73
    • Merge Requests 73
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #5618

Closed
Open
Opened Sep 02, 2020 by Nick Nguyen@nhxnguyenDeveloper

Account for seed project in replicate-geo-database

Summary

Recently, we added a self-monitoring seed project for fresh GitLab installs (gitlab#208454 (closed)).

When 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 gitlab_is_active? returns true.

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?

When running 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.

Relevant logs

Relevant logs

Details of package version

Provide the package version installation details

Edited Sep 04, 2020 by Nick Nguyen
Assignee
Assign to
13.7
Milestone
13.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/omnibus-gitlab#5618