pkgs.fedoraproject.org is not reachable from inside Fedora infra and therefore task-modularity-testing-framework fails to run:
pkgs.fedoraproject.org
+ fedpkg clone -a modules/dhcp-server Cloning into 'dhcp-server'... fatal: unable to connect to pkgs.fedoraproject.org: pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out Could not execute clone: Command '['git', 'clone', 'git://pkgs.fedoraproject.org/modules/dhcp-server', '--origin', 'origin']' returned non-zero exit status 128
http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/440648/steps/runtask/logs/stdio
This will be definitely shown in the next Modularity demo. Sprint #29. Please fix it asap. We will do hackfest Tue 25 and would be fine to fix the issue before it.
Thanks for solving the issue soon.
Filed issue with fedpkg to fix the problem: https://pagure.io/fedpkg/issue/119
When is the next modularity demo?
I've submitted a PR to fix the issue:
https://pagure.io/fedpkg/pull-request/120
It should be solved ideally during Monday 24th. We will build huge set of modules during Tuesday 25th and testing would go over taskotron.
Thanks for issue and PR.
After reading the PR response and looking over the bug, I think this will take a longer time to resolve. However, you can do a temporary workaround in modularity-testing-framework - copy the fedpkg config to a temp dir, modify it and then use fedpkg --config. See https://pagure.io/fedpkg/pull-request/120#request_diff to see the necessary changes. I tried it and it works.
fedpkg --config
The fedpkg config change should not be required to work anymore since I have just updated DNS so the internal IP is used for access to pkgs.fp.o, which should resolve this issue in the short term.
I can confirm this is now working. No need for modularity-testing-framework workaround anymore. Thanks, @puiterwijk!
Metadata Update from @kparal: - Issue tagged with: infrastructure
Login to comment on this ticket.