Page MenuHomeSoftware Heritage

jenkins: Unstuck buster-swh image build
Closed, MigratedEdits Locked

Description

Currently, due to a recent change to add a new dependency, we had to rebuild the docker image.
The build [1] is stuck for unrelated reasons.

Which results in a poor coverage from for example this diff [2].

Somehow, we cannot retrieve the cassandra release keys from download.apache.org.
The curl query is stuck from our networks.

Idea from @vsellier: using a mirror of it.

[1] https://jenkins.softwareheritage.org/job/jenkins-tools/job/swh-jenkins-dockerfiles/1136/console

[2] D8636

Event Timeline

ardumont triaged this task as High priority.Oct 7 2022, 5:18 PM
ardumont created this task.
17:14 <vsellier> ardumont: https://dlcdn.apache.org/  <-- an apache download mirror
17:14 <+ardumont> cool, thx
17:15 <+ardumont> $ curl -s https://dlcdn.apache.org/cassandra/KEYS | sha256sum
17:15 <+ardumont> 2235af6fadff786479aa2c59574a81c97260a8a33fdda426337dc6ea783859e9  -
17:15 <+ardumont> $ curl -s https://downloads.apache.org/cassandra/KEYS | sha256sum
17:15 <+ardumont> 2235af6fadff786479aa2c59574a81c97260a8a33fdda426337dc6ea783859e9  -
ardumont renamed this task from Unstuck buster-swh image build to jenkins: Unstuck buster-swh image build.Oct 7 2022, 5:19 PM

More importantly:

ardumont@thyssen:~% curl -s https://dlcdn.apache.org/cassandra/KEYS | sha256sum
2235af6fadff786479aa2c59574a81c97260a8a33fdda426337dc6ea783859e9  -

Apparently we're blocked somewhere at hertzner:

% tcptraceroute downloads.apache.org
Selected device vlan1300, address XXX, port 49995 for outgoing packets
Tracing the path to downloads.apache.org (88.99.95.219) on TCP port 80 (http), 30 hops max
 1  xxx
 2  xxx 
 3  * * *
 4  xe1-1-10-paris1-rtr-131.noc.renater.fr (193.51.177.106)  1.101 ms  1.038 ms  1.018 ms
 5  renater-ias-geant-gw.par.fr.geant.net (83.97.89.9)  1.470 ms  1.343 ms  1.259 ms
 6  ae5.mx1.gen.ch.geant.net (62.40.98.182)  18.107 ms  18.143 ms  17.893 ms
 7  ae2.mx1.fra.de.geant.net (62.40.98.180)  17.804 ms  27.069 ms  18.987 ms
 8  * * *
 9  core24.fsn1.hetzner.com (213.239.252.42)  20.140 ms  20.348 ms  19.926 ms
10  ex9k1.dc1.fsn1.hetzner.com (213.239.245.234)  19.754 ms  19.677 ms  20.425 ms
11  * * *
...

It's unstucking the build buster-swh but still the kafka image is failing for mostly the same initial reason.
It's fetching old kafka versions in the archive mirror unreachable from our infra [1].

Those versions are not present in the mirror [2] (starting at 2.8.2 and we want 2.6.0).

https://jenkins.softwareheritage.org/blue/organizations/jenkins/jenkins-tools%2Fswh-jenkins-dockerfiles/detail/swh-jenkins-dockerfiles/1142/pipeline

[1] https://archive.apache.org/dist/kafka/2.6.0/kafka_2.13-2.6.0.tgz

[2] https://dlcdn.apache.org/kafka/

I've tested with the ips closed to the apache ones (88.99.95.218 and 88.99.95.220) and we can reach them, so we are probably blocked somewhere in the apache's infra

ardumont claimed this task.
ardumont moved this task from deployed/landed/monitoring to done on the System administration board.