2019-09-02 - Triage report for "group::geo"

Hi, @fzimmer @rnienaber @andr3

This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:

  • https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages

Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:

  • Determine if the issue should be closed if it is no longer relevant or a duplicate.
  • If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
  • Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
    • https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#priority-labels
  • Once a milestone has been assigned please check off the box for that issue.
  • Please work with your team to complete the list by the due date set.

Unscheduled feature (non-customer)

  • #14631 (closed) Add secondary lag message on Git push over SSH ~"Geo : Replication Lag Warning", feature, groupgeo
  • #13720 Restrictive selective synchronisation feature, geoplanning, groupgeo, ~"problem validation", ~"product discovery"
  • #13029 Selective sync for replicated Docker registries ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", customer+, devopsenablement, feature, geoplanning, groupgeo, ~"planning breakdown"

Bug Section

For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.

Heatmap for all bugs

Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.

~S1 ~S2 ~S3 ~S4 ~"No severity"
~P1 0 0 0 0 0
~P2 0 0 0 0 0
~P3 0 0 16 5 0
~P4 0 0 2 8 0
~"No priority" 0 0 0 0 1

Unscheduled frontend ~bug (non-customer)

  • #8154 (closed) Geo: Cursor events not displayed in /admin/geo/nodes screen ~"Accepting merge requests", Geo Administration, ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S4", ~"bug", devopsenablement, frontend, groupgeo, regression, regression:11.4
  • #7707 (closed) Geo: Progress bars incorrectly display Infinity ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P4", ~"S4", ~"bug", devopsenablement, frontend, groupgeo
  • #7035 (closed) "Storage config" section makes no sense for primary ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S4", ~"bug", devopsenablement, frontend, groupgeo

Unscheduled ~bug (non-customer)

  • #11261 (closed) Geo OAuth session authorize_url may not handle relative_url_root Geo Administration, ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P4", ~"S3", ~"bug", devopsenablement, geotriage, groupgeo
  • #9803 Geo: Handle moving project repository storage ~"Geo Replication/Sync", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P4", ~"S4", ~"bug", devopsenablement, geotriage, groupgeo
  • #8021 (closed) Geo: Do better at ensuring important jobs are run, e.g. after transient problems ~"Accepting merge requests", ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", data integrity, devopsenablement, groupgeo
  • #7977 (closed) Geo: Ensure both the repo and wiki gets synced if an RepositoryUpdatedEvent is processed before the project is backfilled, or if RepositoryUpdatedEvent is processed before RepositoryCreatedEvent ~"Accepting merge requests", ~"Geo DR", ~"Geo Replication/Sync", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", data integrity, devopsenablement, geotriage, groupgeo
  • #7559 (closed) 'The redirect URI included is not valid.' error OAuth'ng a secondary Geo Administration, ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S4", ~"bug", devopsenablement, groupgeo
  • #7199 (closed) Geo: last-processed event ID is sometimes larger than maximum event ID ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", database, devopsenablement, geotriage, groupgeo, ha
  • #7156 (closed) Geo::RenameRepositoryWorker: NoMethodError: undefined method `date' for nil:NilClass ~"Geo Replication/Sync", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", auto updated, ~"bug", devopscreate, geotriage, groupgeo
  • #7111 (closed) Git fsck parallelism not properly spread out over shards on Geo secondary ~"Geo Performance", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S4", auto updated, awaiting feedback, ~"bug", devopsenablement, geotriage, groupgeo
  • #6867 (closed) Improve Geo failures API handling of unknown types Geo Administration, ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P4", ~"S4", api, ~"bug", devopsenablement, groupgeo
  • #6350 (closed) Geo: issue boards can't pre-populate on secondary node ~"Geo Replication/Sync", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", devopsenablement, groupgeo
  • #6143 (closed) [Geo] Invalid repositories can't be synced GCP Migration, ~"Geo Replication/Sync", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", devopsenablement, groupgeo
  • #5994 (closed) Geo: After DB went down and back up, large number of ProjectImportScheduleWorker jobs ran Geo Administration, ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", devopsenablement, geotriage, groupgeo
  • #5826 (closed) [Geo] File transfer logs errors are logged in a wrong way ~"Accepting merge requests", ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P4", ~"S4", ~"bug", devopsenablement, groupgeo
  • #5575 (closed) Geo: Job artifact deleted event could not be created ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P4", ~"S3", ~"bug", devopsenablement, geotriage, groupgeo
  • #5089 (closed) Geo secondary creates empty repositories where the primary has no repository ~"Geo Verification/Accuracy", ~"Geo [DEPRECATED]", ~"GitLab Enterprise Edition", ~"P3", ~"S3", ~"bug", default-priority, default-severity, devopsenablement, groupgeo


This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:

  • https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages
Edited Sep 03, 2019 by Fabian Zimmer
Assignee Loading
Time tracking Loading