GitLab Registry Pod Not Running After Upgrade to 17.6.1

Summary

After upgrading GitLab from version 17.5.2 to 17.6.1 using the BigBang Helm chart 8.3.6-bb.1, the gitlab-registry pod is not reaching a running state. This issue is blocking the GitLab registry functionality.

Steps to reproduce

1. Upgraded GitLab from 17.5.2 to 17.6.1 to resolve CVEs using BigBang Helm chart 8.3.6-bb.1.
2. Deployed using the following image for the GitLab registry: registry1.dso.mil/ironbank/gitlab/gitlab/gitlab-container-registry:17.6.1
3. Observed the gitlab-registry pod status.

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

The gitlab-registry pod is not running. The logs suggest the service initializes but does not progress to a Running state.

Relevant logs and/or screenshots

Below are the logs from the gitlab-registry pod:

{"go_version":"go1.23.2","instance_id":"051176e6-3978-4885-936b-e01ee91fe704","level":"info","msg":"backend redirection disabled","service":"registry","time":"2024-12-02T18:24:51.259Z","version":"v4.13.0-gitlab"}
{"go_version":"go1.23.2","instance_id":"051176e6-3978-4885-936b-e01ee91fe704","level":"info","msg":"Starting upload purge in 51m0s","service":"registry","time":"2024-12-02T18:24:51.342Z","version":"v4.13.0-gitlab"}

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Tasks

• Bug has been identified and corrected within the container