Git clone error -- fatal: remote transport reported error

3,501 views
Skip to first unread message

Prabhu kondarangi

unread,
Feb 7, 2022, 6:06:20 AM2/7/22
to Repo and Gerrit Discussion
Hi Team,

I am unable to clone my project with git latest version  2.33.*  and above,  but I am able to clone with a lower version 2.32.* and below.

Please find the git clone output as follows.

------------------------------------------------------------------------------------------------------------------------------
vijay@server:~$ git --version
git version 2.33.1

vijay@server:~/test_clone$ git clone ssh://I...@gerrit.server/test-project
Cloning into 'test-project'...
fatal: remote transport reported error
------------------------------------------------------------------------------------------------------------------------------
vijay@server:~$ git --version
git version 2.32.0

vijay@server:~/test_clone$ git clone ssh://I...@gerrit.server/test-project
Cloning into 'test-project'...
warning: remote HEAD refers to nonexistent ref, unable to checkout.
------------------------------------------------------------------------------------------------------------------------------

My project HEAD is pointing to the master branch which does not exist.

As I am trying to fix the git clone issue here, I am not supposed to change the project configuration due to some restrictions in the company. (Which is creating a master branch in the project)

Does anyone face this kind of issue?

Is there any fix for the git clone error fatal: remote transport reported error?

Thanks,
Prabhu


Prabhu kondarangi

unread,
Feb 7, 2022, 11:45:30 PM2/7/22
to Repo and Gerrit Discussion
Hi Team,

Can anyone help with this, please?

Regards,
PK

doug.r...@wandisco.com

unread,
Feb 8, 2022, 2:58:17 PM2/8/22
to Repo and Gerrit Discussion
PK:

Have you tried Git 2.34 or above?

Also, try doing the clone with tracing turned on so we can see where things are going wrong:

    $ GIT_TRACE=1 git clone ...

Cheers.

Doug 

Thanks,
Prabhu


Prabhu kondarangi

unread,
Feb 23, 2022, 9:05:24 AM2/23/22
to Repo and Gerrit Discussion
Hi Doug,

I have tried with Git 2.34 and above. It fails with the same here and Git Trace did not help much either.

I would like to provide more details on the project here.
==> My project has a branch/namespace called refs/meta/config but it does not have a branch master. But the HEAD points to master.
Was this a reason for a git clone error fatal: remote transport reported error?

Have you/someone faced this issue with this scenario?

Thanks,
Prabhu

doug.r...@wandisco.com

unread,
Feb 23, 2022, 3:47:07 PM2/23/22
to Repo and Gerrit Discussion
Prabhu:

On Wednesday, February 23, 2022 at 9:05:24 AM UTC-5 prabh...@gmail.com wrote:
I have tried with Git 2.34 and above. It fails with the same here and Git Trace did not help much either.

There are a bunch of TRACE environment variables to work with to see various aspects of your request, see [1].
 
I would like to provide more details on the project here.
==> My project has a branch/namespace called refs/meta/config but it does not have a branch master. But the HEAD points to master.
Was this a reason for a git clone error fatal: remote transport reported error?

Have you thought about changing HEAD to point to something that exists?  If that works to fix things then I suspect that the server is not handling some nuance of the protocol quite right (or they have consistently broken then new Git versions - much less likely but possible).

What version of Gerrit are you running?

Cheers.

Doug

Prabhu kondarangi

unread,
Feb 24, 2022, 1:57:25 AM2/24/22
to Repo and Gerrit Discussion
Doug:

I am using git version 2.35.1.

I was thinking of changing the HEAD point to the existing branch. but it is not recommended in the company.

I will look into Git-Internals-Environment-Variables as well. 

Thomas Wolf

unread,
Feb 24, 2022, 6:29:07 PM2/24/22
to Repo and Gerrit Discussion
On Thursday, February 24, 2022 at 7:57:25 AM UTC+1 prabh...@gmail.com wrote:
Doug:

I am using git version 2.35.1.

I was thinking of changing the HEAD point to the existing branch. but it is not recommended in the company.

[...]

On Wednesday, February 23, 2022 at 9:05:24 AM UTC-5 prabh...@gmail.com wrote:
I have tried with Git 2.34 and above. It fails with the same here and Git Trace did not help much either.

There are a bunch of TRACE environment variables to work with to see various aspects of your request, see [1].
 
I would like to provide more details on the project here.
==> My project has a branch/namespace called refs/meta/config but it does not have a branch master. But the HEAD points to master.
Was this a reason for a git clone error fatal: remote transport reported error?

There were certainly changes in C git in this area.

 

anna.fr...@gmail.com

unread,
Mar 2, 2022, 7:10:10 AM3/2/22
to Repo and Gerrit Discussion
As I understand it newer versions of Git comes with OpenSSH 8.8 which disables older algorithms of RSA and our Gerrit instance seems to be incompatible with the newer variants. I generated a new key pair with ed 25519 and added to Gerrit.

ssh-keygen -t ed25519

Reply all
Reply to author
Forward
0 new messages