The 185.15.57.8/30 subnet is not routed in the cloud edge routing.
This means we can ping some cloud-eqiad IPs but not cloud-codfw.
Example:
arturo@endurance:~ $ ping -c1 virt.cloudgw.codfw1dev.wikimediacloud.org. PING virt.cloudgw.codfw1dev.wikimediacloud.org (185.15.57.9) 56(84) bytes of data. --- virt.cloudgw.codfw1dev.wikimediacloud.org ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms arturo@endurance:~ $ ping -c1 virt.cloudgw.eqiad1.wikimediacloud.org. PING virt.cloudgw.eqiad1.wikimediacloud.org (185.15.56.237) 56(84) bytes of data. 64 bytes from virt.cloudgw.eqiad1.wikimediacloud.org (185.15.56.237): icmp_seq=1 ttl=55 time=120 ms --- virt.cloudgw.eqiad1.wikimediacloud.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 120.035/120.035/120.035/0.000 ms
In eqiad we have cloudsw acting as edge router for the cloud-realm networks.
However, in codfw we don't have cloudsw yet (see T272348), so this change needs to be done in cr-codfw:
--- old.txt 2021-11-08 14:29:36.491466401 +0100 +++ new.txt 2021-11-08 14:30:02.733000579 +0100 @@ -1,4 +1,5 @@ static { [..] route 185.15.57.0/29 next-hop 208.80.153.190; + route 185.15.57.8/30 next-hop 208.80.153.190; }
For reference, cloudsw has this:
static {
route 172.16.0.0/21 next-hop 185.15.56.244;
route 185.15.56.0/25 next-hop 185.15.56.244;
route 185.15.56.236/30 next-hop 185.15.56.244;
}