#9354 Trouble cloning via https fedora-infra/ansible
Closed: Fixed 3 years ago by smooge. Opened 3 years ago by dkirwan.

Describe what you would like us to do:


I'm having trouble cloning the fedora-infra/ansible repo from Pagure.

 git clone https://pagure.io/fedora-infra/ansible.git
Cloning into 'ansible'...
remote: Counting objects: 232977, done.
remote: Compressing objects: 100% (63773/63773), done.
fatal: the remote end hung up unexpectedly98 MiB | 793.00 KiB/s
fatal: early EOF
fatal: index-pack failed

When do you need this to be done by? (YYYY/MM/DD)


N/A


I spoke with @smooge he requested additional information.

I'm based in Ireland/Europe, and the results of a traceroute -n

My public IP: 80.233.33.87

traceroute -n pagure.io
traceroute to pagure.io (8.43.85.75), 30 hops max, 60 byte packets
 1  192.168.8.1  1.906 ms  2.649 ms  2.338 ms
 2  172.24.63.134  70.581 ms  70.314 ms  70.035 ms
 3  172.24.51.197  55.633 ms  55.365 ms  56.139 ms
 4  172.24.194.173  57.047 ms  57.808 ms  57.584 ms
 5  172.24.194.174  71.896 ms  71.723 ms  67.535 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Not sure if it helps:

 git --version
git version 2.26.2

uname -a
Linux fedorable 5.6.14-300.fc32.x86_64 #1 SMP Wed May 20 20:47:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Third time lucky, intermittent issue I guess.

 git clone https://pagure.io/fedora-infra/ansible.git
Cloning into 'ansible'...
remote: Counting objects: 232977, done.
remote: Compressing objects: 100% (63773/63773), done.
remote: Total 232977 (delta 158287), reused 232090 (delta 157632)
Receiving objects: 100% (232977/232977), 72.94 MiB | 427.00 KiB/s, done.
Resolving deltas: 100% (158287/158287), done.

OK I think your ISP is using nat over nat and is having network issues. The traceroute is getting held up inside the ISP and does not seem to reach either 8.43.85.75 or 2620:52:3:1:dead:beef:cafe:fed5 depending if they are also doing an ipv4 2 ipv6 proxy.

Could you also do a

curl http://icanhazip.com
curl -4 http://icanhazip.com

which might help us figure out on the server what is going on.

Sure:

 curl http://icanhazip.com
80.233.33.87
 curl -4 http://icanhazip.com
80.233.33.87

OK David and I worked on IRC and it looks like a transient network issue.

Metadata Update from @smooge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata