Import Fails with missing content and 13:CreateRepositoryFromBundle: cmd wait failed: exit status 128

Symptom seems to be the same as #51693 (closed) but I wasn't sure whether it's actually the same issue since the fix was merged.

When importing a project, the Import seems to succeed with no errors in the UI, however a lot of content does not get imported and logs show:

RuntimeError: Error importing repository into PROJECT PATH - 13:CreateRepositoryFromBundle: cmd wait failed: exit status 128

A customer provided an export which I imported to a private test project. Project export in this case is ~900MB

Results of import:

but I can tell from the package file that there should be lots of issues, MRs, and files that haven't imported.

In other reports, some, but not all issues are imported and over multiple tests, the number of and specific issues that import seem to be random.

In one report, they can checkout the files via command line, but UI is showing an empty repo.

I can only assume that what we're seeing is a partial import of everything that imported before it timed out.

Customer reports (all internal):

Relevant Gitaly log entry period (internal), but unfiltered since I wasn't sure what might be relevant.

GitLab Enterprise Edition 11.4.0-rc8-ee

For current workarounds on self-managed GitLab (includes workaround for exporting out of self-managed), please see https://gitlab.com/gitlab-org/gitlab-ce/issues/52956#note_111473696

For importing into GitLab.com, please consider:

using one or more methods of reducing the repository size
edit the import_export.yaml file on the self-managed instance to export only the most important parts of the project. See example in https://gitlab.com/gitlab-org/gitlab-ce/issues/52956#note_112117847
customers still having problems importing can write into Support and refer to this issue.

Edited Aug 28, 2019 by Cynthia "Arty" Ng