Outage in GitLab

Self-managed runners are failing after runners are upgraded to 17.5

Resolved Minor
October 18, 2024 - Started 3 months ago - Lasted about 11 hours

Need to monitor GitLab outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including GitLab, and never miss an outage again.
Start Free Trial

Outage Details

Self-managed runners are failing with the error "failed to get user home dir: $HOME is not defined" after upgrading the GitLab runner to version 17.5. The current workaround is to downgrade the affected runners back to version 17.4. More details are available in https://gitlab.com/gitlab-org/gitlab-runner/-/issues/38252.
Latest Updates ( sorted recent to last )
3 months ago - at 10/18/2024 09:49AM

Self-managed runners are failing with the error "failed to get user home dir: $HOME is not defined" after upgrading the GitLab runner to version 17.5. The current workaround is to downgrade the affected runners back to version 17.4. More details are available in https://gitlab.com/gitlab-org/gitlab-runner/-/issues/38252.

3 months ago - at 10/18/2024 10:25AM

We have identified the problem and are working on releasing a patch for version 17.5. We will send a new update once the patch is available. For more information please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18732.

Need to know when vendors go down? You’re in the right place

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3279 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required