Container registry garbage collection marking manifests eligible for deletion that may still be referenced
Summary
A customer ran a dry run garbage collection on their container registry and when inspecting the logs determined some manifests were being marked eligible for deletion that appear to still be referenced by tags.
Steps to reproduce
TBD
Example Project
What is the current bug behavior?
The logs indicate the dry run was improperly marking some manifests for deletion.
What is the expected correct behavior?
Garbage collection should only be marking untagged manifests and unreferenced layers as eligible for deletion (see: https://docs.gitlab.com/ee/administration/packages/container_registry.html#removing-untagged-manifests-and-unreferenced-layers )
Relevant logs and/or screenshots
See: https://gitlab.zendesk.com/agent/tickets/288725
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)