Skip to content

Empty Pages causes Replication Failure to Geo Secondary

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

When having empty Pages file that does not exists, because the project does not public anything (no index.html etc.),

GitLab should create an empty file. The file that was not created is entered in the database, which then interferes with checksum while replicating to Geo Secondary site.

Steps to reproduce

  1. On Geo Primary, have empty pages projects
  2. Perform replication to Geo Secondary

Example Project

What is the current bug behavior?

Replication will not be 100% completed due to "File is not checksummable" error.

What is the expected correct behavior?

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.

Edited by 🤖 GitLab Bot 🤖