We have a CI/CD pipeline which downloads various Ubuntu packages with apt. Starting this morning we are seeing most jobs fail with various network errors. Occasionally (about 1 in 10) a job succeeds with no network problems.
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Could not connect to security.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (2001:67c:1562::18). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (185.125.190.39), connection timed out Could not connect to security.ubuntu.com:80 (91.189.91.39), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.36), connection timed out [IP: 185.125.190.36 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/gnupg2/gnupg_2.2.4-1ubuntu1.6_amd64.deb Connection failed [IP: 185.125.190.36 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libx/libxaw/libxaw7_1.0.13-1_amd64.deb Connection failed [IP: 91.189.91.39 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/gsfonts/gsfonts_8.11+urwcyr1.0.7~pre44-4.4_all.deb Could not connect to archive.ubuntu.com:80 (185.125.190.36), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.39), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.39), connection timed out [IP: 91.189.91.39 80]
The Ubuntu archive servers are all up and the Network is Unreachable messages make me think that this is some sort of infrastructure issue. Is anyone else experiencing this? I’d like to avoid diving into this if it’s something that will just get handled on Gitlab’s end.
Thank you!