registry-garbage-collect blows up on moved projects (failed to retrieve tags unknown repository)
Summary
Running gitlab-ctl registry-garbage-collect -m
fails with an error failed to garbage collect: failed to mark: gcs: gcs: failed to retrieve tags unknown repository name=anthony-ldap/customer-portal/feature-container
referring to the old name of a renamed project. This is using Google Cloud Storage for the registry.
Steps to reproduce
Happens each run of gitlab-ctl registry-garbage-collect -m
That project was (a while ago) renamed to services/customer-portal via project settings→advanced→rename repository.
Also, at one point registry storage was migrated from local disk to Google Cloud Storage by copying all the files to objects (using rclone sync
), and changing the GitLab settings.
Example Project
N/A
What is the current bug behavior?
Error message.
What is the expected correct behavior?
A bunch of old, obsolete images deleted.
Relevant logs and/or screenshots
root@git:~# gitlab-ctl registry-garbage-collect -m
ok: down: registry: 0s, normally up
Running garbage-collect using configuration ["/opt/gitlab/embedded/bin/registry", "garbage-collect", "/var/opt/gitlab/registry/config.yml", "-m"], this might take a while...
anthony-ldap/customer-portal/feature-container
manifest eligible for deletion: sha256:1aa45b60b2bbba67c1b33f3ed4c764e8737c49731e934beeb051231b3ed4d4e1
failed to garbage collect: failed to mark: gcs: gcs: failed to retrieve tags unknown repository name=anthony-ldap/customer-portal/feature-container
Failed to run garbage-collect command, starting registry service.
ok: run: registry: (pid 28110) 0s
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
root@git:~# gitlab-rake gitlab:env:infoSystem information System: Debian 9.8 Current User: git Using RVM: no Ruby Version: 2.5.3p105 Gem Version: 2.7.6 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.18.1 Sidekiq Version:5.2.5 Go Version: unknown
GitLab information Version: 11.10.0 Revision: 8a802d1c6b7 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 9.6.11 URL: https://git.«REDACTED».net HTTP Clone URL: https://git.«REDACTED».net/some-group/some-project.git SSH Clone URL: git@git.«REDACTED».net:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers:
GitLab Shell Version: 9.0.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 9.0.0 ? ... OK (9.0.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) DN: cn=«REDACTED» uid: «REDACTED» ⋮ «REDACTED»
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ...
5/2 ... yes 5/3 ... yes 5/4 ... yes 5/5 ... yes 6/6 ... yes 6/7 ... yes 6/8 ... yes 6/9 ... yes 6/10 ... yes 6/11 ... yes 6/12 ... yes 6/13 ... yes 6/14 ... yes 6/15 ... yes 6/16 ... yes 6/17 ... yes 6/18 ... yes 6/19 ... yes 6/20 ... yes 6/21 ... yes 6/22 ... yes 6/23 ... yes 6/24 ... yes 6/25 ... yes 6/26 ... yes 6/27 ... yes 6/28 ... yes 6/29 ... yes 6/30 ... yes 6/31 ... yes 6/32 ... yes 6/33 ... yes 6/34 ... yes 6/35 ... yes 6/36 ... yes 6/37 ... yes 4/38 ... yes 49/39 ... yes 49/40 ... yes 5/41 ... yes 4/42 ... yes 5/43 ... yes 6/44 ... yes 6/45 ... yes 6/46 ... yes 6/47 ... yes 4/50 ... yes 6/52 ... yes 6/53 ... yes 57/54 ... yes 4/55 ... yes 57/56 ... yes 57/57 ... yes 4/58 ... yes 6/59 ... yes 59/61 ... yes 49/62 ... yes 4/63 ... yes 5/64 ... yes 5/65 ... yes 6/66 ... yes 5/67 ... yes 4/68 ... yes 62/69 ... yes 66/70 ... yes 6/71 ... yes 62/72 ... yes 62/73 ... yes 6/74 ... yes 6/75 ... yes 66/76 ... yes 6/77 ... yes 6/78 ... yes 6/79 ... yes 6/80 ... yes 6/81 ... yes 6/82 ... yes 66/83 ... yes 6/84 ... yes 6/85 ... yes 66/86 ... yes 74/87 ... yes 59/88 ... yes 74/89 ... yes 74/91 ... yes 74/92 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.5.3) Git version >= 2.18.0 ? ... yes (2.18.1) Git user has default SSH configuration? ... yes Active users: ... 53
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)