We have set the retention policy to remove tags from certain repos. In the log output I can see the tags are flagged as deleted and on the filesystem I can see increased disk availability.
However, the zot_repo_storage_bytes metric endpoint still reflects the old value. Only after pushing to that specific repo is the metric updated.
I believe this is because the nothing in the GC code ends up calling monitoring.SetStorageUsage(is.metrics, is.rootDir, repo).
zot version
v2.0.3
Describe the bug
We have set the retention policy to remove tags from certain repos. In the log output I can see the tags are flagged as deleted and on the filesystem I can see increased disk availability.
However, the
zot_repo_storage_bytes
metric endpoint still reflects the old value. Only after pushing to that specific repo is the metric updated.I believe this is because the nothing in the GC code ends up calling
monitoring.SetStorageUsage(is.metrics, is.rootDir, repo)
.To reproduce
Expected behavior
To have the
zot_repo_storage_bytes
metric be updated after images are garbage collected.Screenshots
No response
Additional context
No response