Some CI jobs are failing to run due to insufficient permissionsOperational

Components

CI/CD - Hosted runners on Linux

Locations

Google Compute Engine



December 5, 2024 22:50 UTC
[Resolved] No more reports of this error have been received. We conclude the monitoring period and consider this incident resolved. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18952 for details.

December 5, 2024 22:32 UTC
[Monitoring] We would like to clarify that this problem affected some jobs on GitLab.com groups that used the "Restrict group access by IP address" feature. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18952.

December 5, 2024 21:52 UTC
[Monitoring] Configuration changes have been put in place in our infrastructure to potentially mitigate this issue. We are currently monitoring our logs and user reports for confirmation. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18952

December 5, 2024 21:40 UTC
[Investigating] We believe the cause for CI clone failure is related to Group-level IP restrictions. We're reviewing internal logs to confirm. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18952 for more.

December 5, 2024 21:18 UTC
[Investigating] We see reports of some CI Jobs failing to clone repositories with an "insufficient permissions" error. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18952 for details on the investigation.

Back to current status