It looks like there's some network problem, as the Duffy API doesn't seem to be reachable from the OCP pods:
$ ping -c 4 duffy.ci.centos.org PING duffy.ci.centos.org (172.19.0.18) 56(84) bytes of data. --- duffy.ci.centos.org ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3058ms $ tracepath duffy.ci.centos.org 1?: [LOCALHOST] pmtu 8951 1: ip-10-131-0-1.ec2.internal 0.486ms 2: ip-172-26-192-1.ec2.internal 0.125ms pmtu 1500 2: no reply 3: no reply 4: no reply 5: no reply 6: no reply ...
From outside it seems to work fine:
$ ping -c 4 duffy.ci.centos.org PING duffy.ci.centos.org (8.43.84.234) 56(84) bytes of data. 64 bytes from ip-8-43-84-234.rdu2c.centos.org (8.43.84.234): icmp_seq=1 ttl=46 time=117 ms 64 bytes from ip-8-43-84-234.rdu2c.centos.org (8.43.84.234): icmp_seq=2 ttl=46 time=116 ms 64 bytes from ip-8-43-84-234.rdu2c.centos.org (8.43.84.234): icmp_seq=3 ttl=46 time=116 ms 64 bytes from ip-8-43-84-234.rdu2c.centos.org (8.43.84.234): icmp_seq=4 ttl=46 time=116 ms --- duffy.ci.centos.org ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 116.106/116.441/117.107/0.394 ms
Today, on internal channels, I noticed there's some unplanned outage in RDU2, maybe it's related to that? Hopefully it's not another cut fiber cable :)
yes, same issue as last time, and network issues impacting all projects hosted in that DC. For your own ref, you can follow internal ticket INC2804508
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue priority set to: Waiting on External (was: Needs Review) - Issue tagged with: centos-ci-infra, centos-common-infra, high-gain, investigation
Got confirmation that it's now all resolved (internal ticket is also closed)
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.