2024-10-18: GitLab Runner v17.5 breaking bugs
Customer Impact
Self-managed Runners are failing after they are upgraded to 17.5
Current Status
-
2024-10-18T21:30:00Z Runner version 17.5.1 has been released and includes a fix for the "failed to get user home dir: $HOME is not defined" error. No action besides upgrading Runner is required. Visit the following docs for how to upgrade the
gitlab-runner
version: - 2024-10-18T10:00:00Z Self-managed Runners are failing after they are upgraded to 17.5. The current workaround is to downgrade affected Runners back to version 17.4.
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, 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.