Staging Container Registry timing out?

Background

We have a basic end-to-end test that will test AutoDevOps templates only in the staging environment.

Test

The test will...

1. Log into staging.gitlab.com
2. Create a Project via the API, with "auto_devops_enabled": true, "template_name": "rails" in the JSON payload
3. Create a Pipeline via the API with several Auto DevOps specific variables set to disabled. Since this template is Auto DevOps compatible, the Auto DevOps pipeline will run.
4. The Auto DevOps pipeline will attempt to push up a freshly built "rails" image to registry.staging.gitlab.com
5. The Job will spin infinitely

Stacktrace / Screenshot

Expand for Stacktrace

Successfully tagged registry.staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2020.../rails-autodevops-project-template-abc123/master:sha1
Successfully tagged registry.staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2020.../rails-autodevops-project-template-abc123/master:latest
The push refers to repository [registry.staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2020.../rails-autodevops-project-template-abc123/master]
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Preparing
...   : Waiting
...   : Waiting
...   : Waiting
...   : Waiting
...   : Waiting
...   : Waiting
...   : Waiting
...   : Waiting
...   : Waiting
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed
...   : Pushed

See gitlab-org/gitlab#240946 (closed) for more context