Data management: Error message displayed when checksum button is clicked

Summary

When you click on the checksum or checksum all button I get an error banner at the top of the page. The operation does appear to have completed successfully.

Steps to reproduce

  • Navigate to the Data Managerment page: Admin-->Monitoring-->Data Management
  • Select any data type that has checksummable items and click the checksum or checksum all button.

What is the current bug behavior?

When I click on the checksum button for an item (upload, projects) I get an error message banner

What is the expected correct behavior?

There should not be an error message

Relevant logs and/or screenshots

image.png

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
  System information System: Ubuntu 24.04 Proxy: no Current User: git Using RVM: no Ruby Version: 3.2.8 Gem Version: 3.7.1 Bundler Version:2.7.1 Rake Version: 13.0.6 Redis Version: 7.2.11 Sidekiq Version:7.3.9 Go Version: unknown  GitLab information Version: 18.8.2-ee Revision: 75b6aa72896 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 16.11 URL: \[http://34.88.49.19\](http://34.88.49.19) HTTP Clone URL: http://34.88.49.19/some-group/some-project.git SSH Clone URL: git@34.88.49.19:some-group/some-project.git Elasticsearch: no Geo: yes Geo node: Primary Using LDAP: no Using Omniauth: yes Omniauth Providers:  GitLab Shell Version: 14.45.5 Repository storages:  - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell  Gitaly  - default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket - default Version: 18.8.2 - default Git Version: 2.52.GIT

Possible fixes

Root cause

This bug happens on Geo primary sites where the Geo secondary has not been setup yet, on this line: https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/gitlab/geo/replicator.rb?ref_type=heads#L393

When Geo is enabled and there are secondary nodes available, an event is published when verification happens. But when there are no Geo nodes yet, the publish method returns nil which the data_management API considers a failure (see this line)

Fix

TBD!

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 Chloe Fons