High disk quota usage despite artifacts being deleted

Summary

Gitlab forum issue (No solution, but this is affecting multiple people): https://forum.gitlab.com/t/high-disk-quota-usage-despite-artifacts-being-deleted/39300/6

Environment: gitlab.com

Account: Free

I currently have a project that would produce artifacts with an expires_in=1h limit. I recently noticed that my disk quota was almost full; attributing almost 7GB to artifacts. This is unexpected as my artifacts are only around 10M.

I manually checked each CI job, and none of them have a downloadable artifact. That is, there is not a download button next to the job in the job list and a few jobs I looked closely at said that the artifact had expired.

At this point, I am guessing one of two things:

  1. The disk quota counter counts something else as artifacts too. Maybe I’m just not looking correctly.
  2. There is a bug somewhere in Gitlab where expired artifacts are not updating the disk quota.

Does any one have any ideas regarding this bug? I have temporarily stopped producing artifacts, and the disk usage has not changed (as expected).

Thank you.

Steps to reproduce

  1. Create project that produces large artifacts (Small artifacts work as well, but large artifacts emphasize the issue).
  2. Make artifacts expire_in=1m.
  3. Run a few builds (enough to make a noticeable difference in project size).
  4. Navigate to usage quotas (in user settings)
  5. Observe that, despite setting artifacts to expire, there is still disk quota being used by them.

Example Project

https://gitlab.com/taysoftware/diskquotausage

This project has a ci pipeline that downloads all of Shakespeare's works and produces it as an artifact. This is meaningless to me, so let me know if I should transfer permissions or something.

What is the current bug behavior?

I ran this a few times to produce artifacts. When downloaded, the artifact .zip is 3.5M and unzipped is 4.7M. When I look at storage, artifacts take up 13M of data: Screen_Shot_2020-07-13_at_10.34.28_AM

What is the expected correct behavior?

I would expect about 4.7M for the one artifact I have.

Relevant logs and/or screenshots

NA

Output of checks

This bug happens on GitLab.com

Possible fixes

NA