2024-06-06: deployment qa jobs failing to pull image
Customer Impact
N/A
Current Status
Deployments are blocked at the gstg-cny smoke test stage until this gets resolved.
There has been a runner system failure, please try again
ERROR: Job failed: failed to pull image "registry.ops.gitlab.net/gitlab-org/gitlab-build-images/debian-bookworm-ruby-3.1.5:bundler-2.5-docker-24.0.5" with specified policies [always]: Error response from daemon: manifest for registry.ops.gitlab.net/gitlab-org/gitlab-build-images/debian-bookworm-ruby-3.1.5:bundler-2.5-docker-24.0.5 not found: manifest unknown: manifest unknown (manager.go:250:0s)
Seems that gitlab-org/quality/staging!234 (merged) was merged right before the smoke tests started to break, so we reverted it gitlab-org/quality/staging!235 (merged).
That MR updated ref to pipeline-common repo, which has an image update MR: gitlab-org/quality/pipeline-common!428 (diffs)
That image doesn't seem to exist in the ops gitlab-build-images container registry, as suggested by that error message.
This incident can be resolved when the tests pass and deployments are blocked, but there should be further investigation into why that expected image is not available in ops gitlab-build-images container registry.
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in our handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.