Intermittent failure to fetch GitLab remote from pipeline | the remote end hung up unexpectedly
Summary
Have noticed intermittent failures around fetching remotes from a pipeline (trigger-omnibus-env job).
Examples:
- https://gitlab.com/gitlab-org/gitlab/-/jobs/3775003483
- https://gitlab.com/gitlab-org/gitlab/-/jobs/3775003483
Stack trace
Initialized empty Git repository in /builds/gitlab-org/gitlab/.git/
Created fresh repository.
remote: Enumerating objects: 199298, done.
remote: Counting objects: 100% (199298/199298), done.
remote: Compressing objects: 100% (115187/115187), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Steps to reproduce
N/A
Example Project
What is the current bug behavior?
Sometimes the job fails to checkout the relevant repo, seeming due to the remote.
What is the expected correct behavior?
The job can checkout the repo.