git clone error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)

Summary

Steps to reproduce

Just a normal git clone to a repo bigger than 140Mb.

What is the current bug behavior?

Getting an RCP error every time I try to clone a repo of 140Mb. If i try using clone --depth 1 and fetch --unshallow it works just fine.

RCP error

$ git clone https://gitlab.x/y/z.git

Cloning into 'z'...
remote: Enumerating objects: 197700, done.
remote: Counting objects: 100% (197700/197700), 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

Using the two steps

$ git clone https://gitlab.x/y/z.git --depth 1

Cloning into 'z'...
remote: Enumerating objects: 4361, done.
remote: Counting objects: 100% (4361/4361), done.
remote: Compressing objects: 100% (3700/3700), done.
remote: Total 4361 (delta 854), reused 2544 (delta 437)
Receiving objects: 100% (4361/4361), 77.63 MiB | 30.03 MiB/s, done.
Resolving deltas: 100% (854/854), done.
Checking out files: 100% (3782/3782), done.

$ git fetch --unshallow

remote: Enumerating objects: 153639, done.
remote: Counting objects: 100% (153631/153631), done.
remote: Compressing objects: 100% (42084/42084), done.
remote: Total 151422 (delta 110485), reused 146423 (delta 106136)
Receiving objects: 100% (151422/151422), 139.65 MiB | 29.24 MiB/s, done.
Resolving deltas: 100% (110485/110485), completed with 1440 local objects.

What is the expected correct behavior?

A normal git clone.

Results of GitLab environment info

GitLab Enterprise Edition 11.6.3-ee

Installation using Helm Charts:
helm repo add gitlab https://charts.gitlab.io && helm update
helm upgrade --install gitlab gitlab/gitlab