Skip to content

Connectivity issue between isobuilders and Redmine breaks CI

I see lots of ISO builds failing on Jenkins because /usr/local/bin/output_ISO_builds_and_tests_notifications --apikey_file /etc/jenkins/redmine_apikey --rfqa_only --no_notify_builds --no_notify_tests fails to connect to Redmine e.g. https://jenkins.tails.boum.org/job/build_Tails_ISO_feature-15428-rename-htp-pools/3/console. I’ve noticed a few such failures on isobuilder2, not checked the others.

The URL that’s queried in in the build failure log. Trying it via curl on isobuilder2 does not always work. I see no connection to that URL from the python-requests/2.12.4 user agent in Redmine’s access.log.

Pinging redmine.tails.boum.org from isobuilder2 sometimes goes to 198.252.153.98 and sometimes to 10.10.0.3, so I suspect one of them works but not the other (firewall or routing issue?).

If that’s something I broke when renaming labs, please give this back to me. But I haven’t noticed this in the last week (didn’t pay that much attention either).

Related issues

Original created by @intrigeri on 16132 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information