Projects::ImportService Errors with exit status 128

Git error - impact(179 events and 105 users)

Details

• Gitlab::Git::CommandError - $? = 128 from http://gitlab.com/gitlab-org/gitlab/blob/b228b1568657c2a5d5724e6c7eca899bd47193e2/lib/gitlab/git/wraps_gitaly_errors.rb#L14-14 indicating GRPC::BadStatus was received
• GRPC Error

{"created":"@1630923124.508453192","description":"Error received from peer ipv4:10.221.2.160:9999","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"CreateRepositoryFromURL: clone cmd wait: fatal: unable to access 'https://gitlab.com/ltp-digital/templates/project_template/': The requested URL returned error: 301\n: exit status 128","grpc_status":13}

Iteration 👣

It seems that there are different errors that follow the pattern:

Error importing repository *** into *** - 13:CreateRepositoryFromURL: clone cmd wait: fatal: [SPECIFIC ERROR] : exit status 128.

Examples can be seen here (list not exhaustive):

1. could not read Username for [FILTERED] terminal prompts disabled - #270584 (closed)
2. unable to access [FILTERED] The requested URL returned error: 301/302 - #32216
3. unable to access [FILTERED] The requested URL returned error: 500
4. unable to access [FILTERED] OpenSSL SSL_connect: Connection reset by peer in connection to www.***.com:443
5. unable to connect to ***.amazonaws.com: ***.amazonaws.com[0: 34.246.52.214]: errno=Connection timed out
6. repository [FILTERED] not found

These could potentially be worked on one (or few) at a time, which can be decided during refinement. The issues are listed roughly in order or frequency.

Plan

• See latest update - #340435 (comment 713249429)