Search

Companies / GitLab / incidents

GitLab: 500 Errors while pushing file rename to remote when secret detection enabled

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

Affected components: Git Operations

Timeline of updates

  1. identified

    Customers who have secret detection enabled and are pushing a file rename, may encounter a 500 error. The issue has been identified and a fix is being deployed. Please see the issue for details and workaround: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434

  2. investigating

    While testing the fix in our staging environment we have determined the root cause has not been fully identified. We continue to investigate this issue. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for updates.

  3. investigating

    No material updates to share at the moment. We continue investigating the root cause of these errors. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for details.

  4. investigating

    Investigation is still in process as a clear cause has not been identified yet. Please review https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for details.

  5. investigating

    We believe the originally identified root cause is the correct one for this incident. We continue testing the fix in our testing infrastructure to confirm this. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for more detals.

  6. investigating

    We expect to have more information in our test results in ~30 minutes; this investigation continues. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for more details.

  7. identified

    The test results in our pre-production environments are positive. The 500 error is no longer seen. We now wait for the fix to be deployed to production. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for further details.

  8. monitoring

    The fix is now in our production environment, we are now monitoring for any new reports of the error before considering this incident resolved. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for details.

  9. resolved

    We consider this incident resolved as the errors are no longer seen in our production environment. See gitlab.com/gitlab-com/gl-infra/production/-/issues/20434 for all the 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