2025-02-03: CI Runners increase in error ratios
Customer Impact
None, runners that were affected didn't execute any jobs since Oct, 2024. Theoretically, impact could have looked like stuck jobs in a pending state. The affected noise in the logs comprised between 1%-11% of all requests.
Current Status
Initially the incident was raised as an severity2 as we couldn't determine with certainty the user impact, accordingly, we completed a revert of the deployment, and a revert of the root MR in subsequent deployments.
The impact of this incident to users was that any pending jobs may not have been picked up (if the runner manager doesn't exist in the database, and the respective runner also doesn't exist in the new partitioned table ci_runners_e59bb2812d). Since all online runners regularly poll for jobs, we'll see this error regardless of whether there is actual impact to the users (if there are no jobs to be picked up, then the user will have experienced no impact). Eventually, it was clear that all affected runners didn't have any associated recent jobs, hence this incident is also backstage.
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: None, as all the affected runners were orphaned runners that haven't been assigned jobs since at least Oct' 24.
- Service Impact: ServiceCI Runners
- Impact Duration: 04:22 UTC - 07:35 UTC (~3 hours)
- Root cause: RootCauseSoftware-Change
📚 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.