Self-hosted gitlab responds with 500 / "invalid revision or path" after updating from 16.11.2 to 17.0.0
After upgrading from 16.11.2 to 17.0.0 (and also after the upgrade to 17.0.1) in some repos the call of
- $PathToGitLabRepo/-/tree/dev/integration/endpoints?ref_type=heads
shows "An error occurred while fetching commit data." and
- $PathToGitLabRepo/-/refs/dev/logs_tree/integration/endpoints?format=json&offset=0&ref_type=heads
returns a 500.
In gitaly/current we get a
"command.count": 1,
"command.cpu_time_ms": 1,
"command.inblock": 0,
"command.majflt": 0,
"command.maxrss": 397940,
"command.minflt": 171,
"command.oublock": 0,
"command.real_time_ms": 1,
"command.spawn_token_fork_ms": 0,
"command.spawn_token_wait_ms": 0,
"command.system_time_ms": 0,
"command.user_time_ms": 1,
"component": "gitaly.StreamServerInterceptor",
"correlation_id": "01HYHYQZ4M27XGEETH45D74BQW",
"error": "invalid revision or path",
"error_metadata": {
"path": "integration/endpoints?ref_type=heads",
"revision": "refs/heads/dev"
},
"grpc.code": "InvalidArgument",
"grpc.meta.auth_version": "v2",
"grpc.meta.client_name": "gitlab-web",
"grpc.meta.deadline_type": "regular",
"grpc.meta.method_operation": "accessor",
"grpc.meta.method_scope": "repository",
"grpc.meta.method_type": "server_stream",
"grpc.method": "GetTreeEntries",
"grpc.request.deadline": "2024-05-23T07:28:52.076",
"grpc.request.fullMethod": "/gitaly.CommitService/GetTreeEntries",
"grpc.request.glProjectPath": "next/solution-repos/qioptiq",
"grpc.request.glRepository": "project-3956",
"grpc.request.payload_bytes": 199,
"grpc.request.repoPath": "@hashed/be/63/be63eccb7b3825f0859ad5293b877aaf3c4e936377dd8234b0ec7ef8b043d6ef.git",
"grpc.request.repoStorage": "default",
"grpc.response.payload_bytes": 0,
"grpc.service": "gitaly.CommitService",
"grpc.start_time": "2024-05-23T07:28:22.976",
"grpc.time_ms": 1.741,
"level": "info",
"msg": "finished streaming call with code InvalidArgument",
"pid": 3908698,
"remote_ip": "10.237.17.28",
"span.kind": "server",
"system": "grpc",
"time": "2024-05-23T05:28:22.978Z",
"user_id": "124",
"username": "ABC"
}
all other log-entries with the correlation_id are only from type info.
Also there are strange /**-entries in the repo.
Edited by Marc Gebauer