2020-06-08 - Triage report for "group::geo"
Hi, @fzimmer @nhxnguyen
This is a group or stage level triage report that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
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.
- 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.
feature (non-customer)
Unscheduled- #220543 (closed) Geo: Investigate better observability of big files transfers Geo Administration, UX, devopsenablement, feature, frontend, groupgeo
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 | 1 | 0 | 0 |
~P3 | 0 | 1 | 22 | 3 | 0 |
~P4 | 0 | 0 | 9 | 13 | 0 |
No priority | 0 | 0 | 2 | 3 | 21 |
customer
Unscheduled ~bug with- #220016 Syncing repos with many branches using Geo fails ~"bug", customer, devopsenablement, groupgeo
- #209988 (closed) Geo: Redownloading repositories via snapshot does not work Category:Geo Replication, ~"P3", ~"S2", ~"bug", customer, devopsenablement, geoactive, groupgeo
- #209320 (closed) Geo: gitlab-psql user password fails for postgres-exporter Category:Geo Replication, ~"P2", ~"S3", ~"bug", customer, devopsenablement, groupgeo
- #202693 (confidential) ~"(confidential)"
- #196213 (closed) Backup process fails with DeadlineExceeded for emptiness check Category:Backup/Restore of GitLab instances, ~"bug", customer, devopsenablement, groupgeo
-
#118459 (closed) Restoring a project's wiki with
gitlab-backup restore
fails if it already exists Category:Backup/Restore of GitLab instances, ~"bug", customer, ~"devops", devopsenablement, groupgeo - #37135 (closed) Sidekiq workers get automatically re-enabled when disabled from the UI ~"P4", ~"S3", ~"bug", customer, devopsmanage, groupgeo, workflowscheduling
- #29780 (closed) Creation of merge_request_diff_commits table and related indices times out when restoring from backup Category:Backup/Restore of GitLab instances, ~"bug", customer, database, devopsenablement, groupgeo
- #27076 (closed) ERROR: relation "xxx" does not exist Category:Backup/Restore of GitLab instances, ~"bug", customer, devopsenablement, groupgeo
- #26246 (closed) Backups are not cleaned up when using S3 ~"Accepting merge requests", Category:Backup/Restore of GitLab instances, For Scheduling, ~"P3", ~"S3", ~"bug", customer, devopsenablement, groupgeo
- #22442 (closed) Unable to restore from backup file Category:Backup/Restore of GitLab instances, ~"bug", customer, devopsenablement, groupgeo
- #22249 (closed) gitlab:backup:restore does not clean tmp directory in backups directory Category:Backup/Restore of GitLab instances, ~"bug", customer, devopsenablement, groupgeo
-
#5267 Unclean kill of sidekiq meant the repository sync didn’t happen.
Failed to obtain exclusive lease
~"Accepting merge requests", Category:Geo Replication, Enterprise Edition, ~"P4", ~"S3", ~"bug", customer, devopsenablement, groupgeo - #20018 (closed) Backup skips repositories where HEAD pointing to a non-existent master branch Category:Backup/Restore of GitLab instances, Create [DEPRECATED], Manage [DEPRECATED], ~"P3", ~"S3", awaiting feedback, backend, ~"bug", customer, default-priority, default-severity, devopsenablement, groupgeo, rake tasks
- #19347 (closed) Backup restore SKIP option (omnibus) Category:Backup/Restore of GitLab instances, Create [DEPRECATED], Manage [DEPRECATED], ~"P3", ~"S3", backend, ~"bug", customer, default-priority, default-severity, devopsenablement, groupgeo
Unscheduled ~bug (non-customer)
- #220091 (closed) Displayed projects creation dates reset after hashed storage migration ~"bug", devopsenablement, groupgeo
- #220026 (closed) Projects 404 after a backup restore Category:Backup/Restore of GitLab instances, ~"S3", ~"bug", devopsenablement, groupgeo
- #217980 (closed) Backup restore task does not create backup directory automatically Category:Backup/Restore of GitLab instances, ~"P4", ~"S4", ~"bug", devopsenablement, groupgeo
- #217880 (closed) Geo: Endpoints that facilitate proxying Git SSH requests may need to check the Geo IP whitelist ~"P4", ~"S4", ~"bug", devopsenablement, groupgeo, security
-
#217631 (closed) ActiveRecord is not responding
connected?
with true ~"P3", ~"S3", ~"bug", devopsenablement, groupgeo, rails6 - #215085 Geo GraphQL API: querying geoNode by name not working ~"bug", devopsenablement, groupgeo
- #214514 (confidential) ~"(confidential)"
- #212936 (closed) GitLab sometimes failed in processing the backups, particularly in the phase of uploading Category:Backup/Restore of GitLab instances, ~"bug", devopsenablement, groupgeo
- #211393 (closed) Docs feedback: Missing Entry in "Excluding specific directories from the backup" ~"S4", ~"bug", devopsenablement, docs-missing, documentation, groupgeo
- #210591 (closed) Geo - ActiveRecord::StatementInvalid: PG::ReadOnlySqlTransaction: ERROR: cannot execute INSERT in a read-only transaction ~"bug", devopsenablement, groupgeo
- #207023 (closed) Backup performance Category:Backup/Restore of GitLab instances, ~"S4", ~"bug", devopsenablement, groupgeo, ~"performance"
- #201877 (closed) GitLab restore hangs / is stuck on epoll_wait Category:Backup/Restore of GitLab instances, backend, ~"bug", devopsenablement, groupgeo
- #121474 (closed) rake aborted! when try backup gitlab Category:Backup/Restore of GitLab instances, ~"S3", ~"bug", devopsenablement, groupgeo
- #118577 (closed) Geo: Reduce scheduler lease timeout ~"bug", devopsenablement, groupgeo
- #11173 (closed) Git push SSH proxy may not handle relative_url_root ~"Accepting merge requests", Enterprise Edition, Geo Administration, ~"P3", ~"S4", ~"bug", devopsenablement, groupgeo
- #9803 Geo: Handle moving project repository storage Category:Geo Replication, Enterprise Edition, ~"P4", ~"S4", ~"bug", devopsenablement, groupgeo, workflowscheduling
- #8117 (closed) Geo: Handle orphaned uploads ~"Accepting merge requests", Category:Geo Replication, Enterprise Edition, ~"P4", ~"S4", ~"bug", devopsenablement, groupgeo
- #18927 (closed) gitlab:backup:restore fails with NoMethodError: undefined method `full_path' for nil:NilClass Category:Backup/Restore of GitLab instances, Create [DEPRECATED], Manage [DEPRECATED], ~"P4", ~"S3", backend, ~"bug", default-priority, default-severity, devopsenablement, groupgeo
- #17016 (closed) GitLab restore does not include custom_hooks Category:Backup/Restore of GitLab instances, Create [DEPRECATED], Manage [DEPRECATED], ~"P4", ~"S3", backend, ~"bug", default-priority, default-severity, devopsenablement, groupgeo
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group_definition.rb.