On Wed, 27 May 2020 at 02:28, Adam Williamson adamwill@fedoraproject.org wrote:
On Wed, 2020-05-27 at 01:20 +0200, Miro Hrončok wrote:
Hello.
There is a docker/podman container image part of the Fedora Python
Classroom Lab:
https://labs.fedoraproject.org/en/python-classroom
I need help with two main issues:
The container doesn't built for Fedora 32:
https://koji.fedoraproject.org/koji/taskinfo?taskID=45001647
But I get an error I don't understand (dnf exited with error, but I see
no error
message).
Errors seem to be in x86_64.log:
2020-05-26 09:59:39,727 - atomic_reactor.util - DEBUG - Step 6/11 : RUN dnf -y --setopt=install_weak_deps=false --disablerepo rawhide-modular install "@python-classroom" nano openssh-clients vim-enhanced wget man && dnf clean all 2020-05-26 09:59:40,900 - atomic_reactor.util - DEBUG - ---> Running in 75ba910cc4cc 2020-05-26 09:59:42,917 - atomic_reactor.util - DEBUG - [91mNo repository match: rawhide-modular 2020-05-26 09:59:42,917 - atomic_reactor.util - DEBUG - [0m 2020-05-26 09:59:43,110 - atomic_reactor.util - DEBUG - atomic-reactor-koji-plugin-f32-container-candid 4.1 kB/s | 413 B 00:00 2020-05-26 09:59:43,289 - atomic_reactor.util - DEBUG - Fedora 32 openh264 (From Cisco) - x86_64 34 kB/s | 5.1 kB 00:00 2020-05-26 09:59:43,542 - atomic_reactor.util - DEBUG - Fedora Modular 32
- x86_64 20 MB/s | 4.9 MB 00:00
2020-05-26 09:59:44,455 - atomic_reactor.util - DEBUG - Fedora Modular 32
- x86_64 - Updates 6.4 MB/s | 1.6 MB 00:00
2020-05-26 10:03:19,281 - atomic_reactor.util - DEBUG - Fedora 32 - x86_64
- Updates 0.0 B/s | 0 B 03:34
2020-05-26 10:03:19,282 - atomic_reactor.util - DEBUG - [91mErrors during downloading metadata for repository 'updates': 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirrors.dotsrc.org/fedora-buffet/fedora/linux/updates/32/Everything/x... [Failed to connect to mirrors.dotsrc.org port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for https://mirror.lzu.edu.cn/fedora/updates/32/Everything/x86_64/repodata/repom... [Failed to connect to mirror.lzu.edu.cn port 443: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirrors.ircam.fr/pub/fedora/linux/updates/32/Everything/x86_64/repoda... [Failed to connect to mirrors.ircam.fr port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://fedora.cu.be/linux/updates/32/Everything/x86_64/repodata/repomd.xml [Failed to connect to fedora.cu.be port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirror.math.princeton.edu/pub/fedora/linux/updates/32/Everything/x86_... [Failed to connect to mirror.math.princeton.edu port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirror.metrocast.net/fedora/linux/updates/32/Everything/x86_64/repoda... [Failed to connect to mirror.metrocast.net port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/... [Failed to connect to mirrors.chroot.ro port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirror.init7.net/fedora/fedora/linux/updates/32/Everything/x86_64/rep... [Failed to connect to mirror.init7.net port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://download-ib01.fedoraproject.org/pub/fedora/linux/updates/32/Everythin... [Failed to connect to download-ib01.fedoraproject.org port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for https://pubmirror1.math.uh.edu/fedora-buffet/fedora/linux/updates/32/Everyth... [Failed to connect to pubmirror1.math.uh.edu port 443: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for https://fedora.mirror.liteserver.nl/linux/updates/32/Everything/x86_64/repod... [Failed to connect to fedora.mirror.liteserver.nl port 443: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for https://mirror.netcologne.de/fedora/linux/updates/32/Everything/x86_64/repod... [Failed to connect to mirror.netcologne.de port 443: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for https://mirrors.lug.mtu.edu/fedora/linux/updates/32/Everything/x86_64/repoda... [Failed to connect to mirrors.lug.mtu.edu port 443: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://mirrors.lug.mtu.edu/fedora/linux/updates/32/Everything/x86_64/repodat... [Failed to connect to mirrors.lug.mtu.edu port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for http://ftp-stud.hs-esslingen.de/pub/fedora/linux/updates/32/Everything/x86_6... [Failed to connect to ftp-stud.hs-esslingen.de port 80: Connection refused] 2020-05-26 10:03:19,283 - atomic_reactor.util - DEBUG - - Curl error (7): Couldn't connect to server for https://mirror.init7.net/fedora/fedora/linux/updates/32/Everything/x86_64/re... [Failed to connect to mirror.init7.net port 443: Connection refused]
etc. etc.
At first glance you'd think it's a network issue, but note it *did* successfully retrieve metadata for several other repos first. What I'd guess is that it works so long as it hits up a mirror within infra, but it seems to not be doing that and instead trying to connect to external mirrors, which presumably it's not allowed to route out to. The question I guess would be why it's getting an infra mirror for the other repos but apparently not for the updates repo. Not sure why that would be, off the top of my head.
So this happen if you are unlucky enough to try to build a container image while the update repo is generated. It seems to happen quite often recently (https://pagure.io/releng/issue/9435) but I honestly not sure how we can improve the situation here :(.
-- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
python-devel@lists.fedoraproject.org