Search

Companies / GitLab / incidents

GitLab: A MacOS Runner is failing jobs

Impact: majorStatus: resolvedStarted Resolved (6.3 h)10 updatesSource: status.gitlab.com (opens in new tab)

Affected components: CI/CDCI/CD - Hosted runners on macOS

Timeline of updates

  1. investigating

    We've received reports that jobs that run on a specific macOS GitLab Runner (with the tag `saas-macos-large-m2pro`) have been failing with a “context deadline exceeded” error. We are in the process of investigating. As a workaround, you can switch to other runners. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details

  2. investigating

    Investigation is ongoing, and we're reviewing relevant runbooks for additional troubleshooting steps. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details

  3. investigating

    No material updates to report. We continue troubleshooting the runner's unavailability. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details

  4. investigating

    We continue investigating the root cause. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details

  5. investigating

    Latest troubleshooting results point a networking issue preventing connectivity with the affected macOS Runner. Investigation continues at gitlab.com/gitlab-com/gl-infra/production/-/issues/20878.

  6. investigating

    We continue to troubleshoot network connectivity for the affected Runner, no material updates to report. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.

  7. investigating

    We have identified a misconfiguration in our Runner infrastructure's routing policies as the potential cause for this issue. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.

  8. investigating

    No material updates to share. We appreciate your patience while we continue investigating this issue, please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.

  9. identified

    We have identified the configuration causing network disruption with the affected Runner and we are working on fixing it. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.

  10. resolved

    We have completed the infrastructure restoration tasks to fix the connectivity issue with the affected Runner. Since 17:51 UTC jobs on this Runner are being processed normally. This is now resolved.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON