Artifacts with nil expiration date

Summary

This issue is promoted from an internal issue.

A SaaS customer is seeing artifacts not being automatically removed.

After investigating a sample repository it looks like the artifact expiration date is nil for some pipelines.

We checked a few examples and saw that the pipelines are:

  • Not the latest
  • Finished successfully
  • For the same branch(main)
  • Started by the same user

During the investigation we validated that:

At that point in time GitLab.com was at release 16.7.7. While investigating the problem simply stopped reproducing, and since the log retention on GitLab.com is 7 days, we could not investigate further.

We recently had a self-managed customer reporting the same behaviour. They were on version 16.7.7, but the problem kept reproducing even after they upgraded to 16.10.4.

Zendesk tickets: 524646, 484239

Steps to reproduce

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

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)

Possible fixes

Edited by 🤖 GitLab Bot 🤖