Companies / GitLab / incidents

GitLab: CI/CD pipelines remain stuck in running status

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

Affected components: CI/CD

Timeline of updates

  1. identified

    Pipelines affected by a previous incident on 3/5 continue to be stuck in Running status. We are working on a process to identify and safely correct these stuck pipelines, and will update this notice once that remediation is in place. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details.

  2. identified

    After consideration, we have decided not to automatically change previously stuck pipelines. Doing so could cause unsafe or stale state changes, for example around deployments and environments.

  3. resolved

    If a pipeline still appears stuck, please cancel and retry the affected job or pipeline. Protections deployed during this incident will prevent this in new pipelines. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for complete details.

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