2023-01-05: The loadbalancer SLI of the ci-runners service (`main` stage) has an error rate violating SLO
Current Status
Error rates for runners trying to post status and job logs spiked from 15:20 UTC to 16:43 UTC. All other Web and API for GitLab.com has been operating normally. Jobs started between 15:20 UTC and 16:07 UTC may have been unable to add to their job log or post their status. Retrying jobs will have them succeed.
A post-deploy migration bump_default_partition_id_value_for_ci_tables
failed, causing a substantial elevation in requests to the patroni-ci
database shard, and this had knock-on effects for error ratios in other services including ci-runners
and api
.
Incident review will be written up in #8207 (closed)
📚 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 and/or Hot Patching | 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 out 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.