Till recently I used pod-python-fXX and it worked fine, but because of discussion happening in https://pagure.io/fedora-ci/general/issue/313 I decided to switch to zuul-worker-f35 label. But I'm getting the strange error in the title:
Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start] Traceback (most recent call last): File "/tmp/ansible_command_payload_39s9gy3d/ansible_command_payload.zip/ansible/modules/command.py", line 412, in zuul_run_command File "/usr/lib64/python3.10/threading.py", line 928, in start _start_new_thread(self._bootstrap, ()) RuntimeError: can't start new thread
You can look at the failed job here.
The PR that is failing can be found here.
Ok I see what the problem is. It is related to https://github.com/moby/moby/issues/42680 where we cannot run such new container images (f35 and rawhide) on our current sf.io container manager.
We are in the process of spawning a new manager on a recent Fedora that should solve the issue by ensuring new images run on that new worker. WIP from our side: https://softwarefactory-project.io/r/c/software-factory/sf-infra/+/23886
However in the meantime you could use label: cloud-fedora-35.
Metadata Update from @fbo: - Issue tagged with: Zuul CI
Thanks for the info, I will try to switch to cloud-fedora-35 in the meantime.
I needed to adjust my jobs to cloud-fedora-35, but I'm stuck on creating the virtual env for tox. It's just stuck on installing the dependencies and fail with TIMED_OUT. Any advise, what could be happening there?
See https://fedora.softwarefactory-project.io/zuul/build/9199461074204fa083b99d0482ce8250
Nevermind, found out there are logs for tox available and the issue is in them.
Closing, seems resolved
Metadata Update from @mvadkert: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.