Changes / GitLab / 500 Errors while pushing file rename to remote when secret detection enabled
GitLab: Major incident: 500 Errors while pushing file rename to remote when secret detection enabled
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.gitlab.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: 500 Errors while pushing file rename to remote when secret detection enabled
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-08-27 15:05 UTC
Before: not present
After: 2025-08-27 20:42 UTC
Before: not present
After: Git Operations
Before: not present
After: 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
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: 500 Errors while pushing file rename to remote when secret detection enabled (this change) | Major incident |