2023-10-02: Staging returns 500 errors
Customer Impact
No customer-facing impact (*). Internal-only issue that prevents deployments from taking place in staging (gstg
) and production (gprd
). staging.gitlab.com was also unavailable for about 50 min.
(*) at the time of the incident. Self-managed users upgrading to 16.5 may run into the same issue. Opend https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/24523 to address this.
Current Status
- staging.gitlab.com is available again
- Deployments to
gstg
are unblocked - Deployments to
gprd
are unblocked
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: no customer-facing impact. Deploys to production and staging are blocked. staging.gitlab.com is intermittently unavailable.
- Service Impact: ServiceGitLab Rails in staging environment
- Impact Duration: 12:53 UTC - 14:43 UTC (110 min)
- Root cause: post-deployment migration following gitlab-org/gitlab!132635 (merged)
📚 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.