2023-01-05: The trace_archiving_ci_jobs SLI of the ci-runners service (`main` stage) has an error rate violating SLO
Current Status
We believe that these errors are knock-on effects from earlier in the day (#8204 (closed)) when an incident was caused by a post-deployment migration which set the partition_id of many ci_build_*-related tables to the wrong partition identifier, causing certain meta-activities in the form of API calls to fail for certain jobs.
Errors have ceased since just after 23:00 UTC.
The metric highlighted by the above graph appears to indicate that the alerting page will resolve on its own.
We assume that the failed archive jobs will be picked up and retried in a few hours, but will confirm that assumption in the coming hours.
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.
📚 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.