2025-02-27: Reintroduction of 19539 Increase in 403 failures in CI runners when downloading artifacts
Customer Impact
Some jobs are failing to download artifacts with the error 403.
Current Status
When rolling back in #19377 (closed), we reintroduced the behavior in #19359 (closed)
The fixes for both issues were added to the main branch and deployed to production. This is resolved.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: A small amount of gitlab.com users that tried to run a manual pipeline under specific conditions.
- Service Impact: ServiceCI Runners
- Impact Duration: 2025-02-27 14:00 - 2025-02-27 15:00 (60 minutes)
- Root cause: We rolled back the release to fix #19377 (closed) which inadvertently rolled back the fix for #19359 (closed), reintroducing the incident.
📚 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.