Error 504/404 when updating Fedora:39

Ask Fedora
1

Hello, Recently our (cudaq) CI has been hitting a network issue when attempting to update. You can see the issues in this example - [C++ bridge] Fix for issue 3239 · NVIDIA/cuda-quantum@47271ad · GitHub

#7 [ 2/12] RUN dnf update -y --nobest expat     && dnf install -y --nobest --setopt=install_weak_deps=False wget         python$(echo 3.10 | tr -d .)     && python3.10 -m ensurepip --upgrade
#7 7.253 Fedora 39 - x86_64                              8.2 MB/s |  58 MB     00:07    
#7 7.262 Errors during downloading metadata for repository 'fedora':
#7 7.262   - Status code: 504 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/releases/39/Everything/x86_64/os/repodata/8e09489af54bbd4ab85470d449f0b0afa4a26fc3eb97c1665c741427bbc8f060-filelists.xml.zck (IP: 3.160.13.215)

I know that there was a recent ddos attack - For your information: DDoS affecting most of the fedoraproject.org services - #6 by thephatlee which could be causing this issue.

Is there still known network issues?

I tried reproducing this line locally and I do hit some 504 errors, but dnf seems to handle it locally - this is only reproducible in our CI environment at the moment.

[MIRROR] gpgme-1.20.0-5.fc39.x86_64.rpm: Status code: 404 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/releases/39/Everything/x86_64/os/Packages/g/gpgme-1.20.0-5.fc39.x86_64.rpm (IP: 3.167.217.183)
[MIRROR] libmetalink-0.1.3-32.fc39.x86_64.rpm: Status code: 404 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/releases/39/Everything/x86_64/os/Packages/l/libmetalink-0.1.3-32.fc39.x86_64.rpm (IP: 3.167.217.183)

Thanks in advance for your help.

1 Like
2

Fedora 39 has been EOL for almost a year and gets no updates of any kind
Fedora 40 is also EOL and receives no updates.

If you wish to remain on f39 then updates are non-existent

If you wish to update then please perform the upgrades using dnf at the command line with sudo dnf system-upgrade download --releasever=XX to download the upgrades followed by sudo dnf system-upgrade reboot (Replace the XX with the release version to use for the upgrade and remember that fedora only supports upgrades of 1 or 2 release versions at a time)

Once you have upgraded to f41 then the system will be running dnf5 and the second command would change to sudo dnf offline reboot

1 Like
3

FYI: You can use dnf system-upgrade reboot with dnf5.

4

Spelled without the extra “d”:

dnf system-upgrade reboot
5

Currently your CI tests only against Fedora 38 and 39, which are out of support. It doesn’t have any coverage for Fedora 41 and 42, which are the currently supported Fedora versions.

Probably it’s best to modify the CI test cases to cover F41 and F42 instead of the obsolete versions?

6

These are container images (e.g. ghcr.io/nvidia/fedora:39@sha256:blah) so rather than trying to upgrade, they can just pull an F41 or F42 container image instead.

7

Thanks for the heads up on EOL, I’ll look to update our CI to use supported versions.

8

Doh! Fixed…

9

What about using RHEL or a derivative? RHEL is based on Fedora, but rather than about 13 months of support as you get with Fedora, RHEL and derivatives will provide up to ten years of support.

10

I mean, it’s good that they test their product against Fedora! (We’re looking at a Fedora container instance used for integration testing of code changes here, not at a production system.)

It’s just best to do it against current versions :slightly_smiling_face:

11

My bad. I have read the thread completely wrong.

doh

1 Like
12

So this is actually probably a bug in how the viable mirrorlist is constructed for F39.

Yes F39 is EOL’d and is not receiving updates.. and users are not encouraged to use it. But users are gonna user for user reasons.

The intent is that metalink should be returning valid mirrors for all the releases… for some reason the mirrorlist for F39 is being populated incorrectly.

I also have an F39 laptop… weirdly I’ve had to boot it like 3 times this week to differential analysis something that’s come up in here…hmm.. anyways…

Im able to pull packages from the F39 repos without a problem because for whatever reason the mirrorlist selection algorithm isn’t choosing the problematic cloudfront mirror…but its in the list.. i checked the metalink XML file pulled.

Not sure how or if this will get sorted out, in the meantime you could stop using metalink and select a specific other mirror that you can confirm is valid.

-jef

13

I was figuring it was some mirror issue. I’d rather just use a supported release than spend time forcing fedora:39 to work.

14

That is a prudent and wise decision and I salute you.

mainly because it lets me depower my F39 laptop again.. because having 4 laptops on my desk just feels wrong.

-jef

1 Like
15

Hello, I just wanted to update that I have removed[0] the EOL fedora:{38,39} from our pipelines, and am now using fedora:41. No issues now. I appreciate the fast responses from everyone.

Next step - add Fedora:42 as well.

[0] - Bump to Fedora:41 as Fedora:38/39 are EOL (#3315) · NVIDIA/cuda-quantum@fa9f1c3 · GitHub

2 Likes