Description
We were planning to update using the 26.04 runners as they provide few newer versions of some packages that we currently would need.
But it seems they are currently having some kind of network issues, atleast related to fedora repo mirrors which our actions use.
You can see an example of the issues here: https://github.com/ublue-os/aurora/actions/runs/27349699803/job/81130072006?pr=2367#step:11:479
This happens only on the new 26.04 runners, the 24.04 runners don’t have this issue
Platforms affected
Runner images affected
Image version and build link
https://github.com/ublue-os/aurora/actions/runs/27349699803/job/81130072006?pr=2367#step:11:479
Is it regression?
Expected behavior
it would be able to resolve hostnames and network would work as it should
Actual behavior
lots of these
Updating and loading repositories:
Fedora 44 - x86_64 - Updates Archive ???% | 0.0 B/s | 0.0 B | 00m20s
Curl error (6): Could not resolve hostname for https://fedoraproject-updates-archive.fedoraproject.org/fedora/44/x86_64/repodata/repomd.xml [Could not resolve host: fedoraproject-updates-archive.fedoraproject.org] - https://fedoraproject-updates-archive.fedoraproject.org/fedora/44/x86_64/repodata/repomd.xml
Repro steps
Looks to be pretty easily reproducible when on the 26.04 runners and dealing with fedora based stuff like building their images and using their repos
Description
We were planning to update using the 26.04 runners as they provide few newer versions of some packages that we currently would need.
But it seems they are currently having some kind of network issues, atleast related to fedora repo mirrors which our actions use.
You can see an example of the issues here: https://github.com/ublue-os/aurora/actions/runs/27349699803/job/81130072006?pr=2367#step:11:479
This happens only on the new 26.04 runners, the 24.04 runners don’t have this issue
Platforms affected
Runner images affected
Image version and build link
https://github.com/ublue-os/aurora/actions/runs/27349699803/job/81130072006?pr=2367#step:11:479
Is it regression?
Expected behavior
it would be able to resolve hostnames and network would work as it should
Actual behavior
lots of these
Updating and loading repositories:
Fedora 44 - x86_64 - Updates Archive ???% | 0.0 B/s | 0.0 B | 00m20s
Repro steps
Looks to be pretty easily reproducible when on the 26.04 runners and dealing with fedora based stuff like building their images and using their repos