Kinoite cannot be updated with rpm-ostree update.
rpm-ostree update
error: While pulling fedora/41/x86_64/kinoite: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/f0/JKMRCklUkk+E0KZa6tjydsaJ7I5CKb+_nSomZfZjg.index: Server returned HTTP 502
rpm-ostree update --preview still works.
Same here. Digging at the error, Cloudfront is complaining that it canāt contact the origin server, so guessing a release mirror is a bit sad. Seems intermittent, occasionally the update gets a few fetches deep before hitting a 502.
Iām looking through the Fedora infra team docs, but so far Iām not sure who owns this layer of mirrors, so not sure where to ping. Hopefully this is a localized unhappy mirror and will self-heal, but Iām not familiar with Fedoraās infrastructure, so not sure 
I am getting these same errors:
$ rpm-ostree update
error: While pulling fedora/41/x86_64/kinoite: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/f0/JKMRCklUkk+E0KZa6tjydsaJ7I5CKb+_nSomZfZjg.index: Server returned HTTP 502
Iām guessing a problem with Amazon CloudFront.
Is there a way to auto-change mirrors?
I have the same issue currently.
I will try a manual workaround as I dont know how to refresh mirrors automatically
https://mirrormanager.fedoraproject.org/mirrors/Fedora/41/x86_64
I searched for my country, copied the https link and did a test on the with ping IP.
I then chose the fastest one.
run0 nano /etc/yum.repos.d/fedora.repo
And added this under [fedora]
baseurl=https://reponame.com/fedora/linux/releases/$releasever/Everything/$basearch/os/
This seems to be preferred over the mirrorlist.
But a command to refresh the mirrorlist would be best
Upstream issue: Issue #12427: Server returns HTTP 502 when trying to rollback Fedora Silverblue - fedora-infrastructure - Pagure.io
Same issue on a fresh install of Silverblue.
While pulling fedora/41/x86_64/silverblue: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/8w/UFyT8ra1CS8MOuaTU8dVVs7hBTi2e6dqXpUST916k.index: Server returned HTTP 502
Same here in NL when running rpm-ostree update;
error: While pulling fedora/41/x86_64/sericea: While fetching https://d2uk5hbyrobdzx.cloudfront.net/objects/db/962e0e2b66ad44e4ab4f009e4e316f594e40022281653046e181294872e214.filez: Server returned HTTP 502
Tried changing URL in /etc/ostree/remotes.d/fedora.conf to (this one)[https://d2uk5hbyrobdzx.cloudfront.net] obtained from the mirrors list, gives 502 as well. Itās picked up only when I comment out the contenturl=mirrorslist=... line.
Are there any other mirrors available? I have a feeling it could be a workaround.
PS. pls forgive obvious and trivial mistakes, total newbie here, just finished installing fedora sway atomic.
Same issue:
error: While pulling fedora/41/x86_64/silverblue: While fetching https://d2uk5hbyrobdzx.cloudfront.net/objects/c7/1f1c0d558e3ec243497f434dadf72839e1e646b70cb6cf43dfa6279d3ed320.filez: Server returned HTTP 502
or
error: While pulling fedora/41/x86_64/silverblue: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/JZ/pQB07uwgIf7ehJly_BR+eYqT8IaW3s4_fyHQPiQX4.index: Server returned HTTP 502
I canāt āupgradeā and ārebaseā for the third day.
Is there a workaround? E.g. manually changing the URL for the ugrade? I tried changing the baseurl in /etc/yum.repos.d/{fedora.repo, fedora-updates.repo}, but it has no effect.
Now the āupgradeā succeeded:
ā Receiving objects; 95% (1488/1564) 1,7 MB/s 42,0 MB 2 metadata, 1562 content objects fetched; 42204 KiB transferred in 31 seconds; 47,3 MB content written
Receiving objects; 95% (1488/1564) 1,7 MB/s 42,0 MB... done
Checking out tree 259a500... done
Enabled rpm-md repositories: fedora-cisco-openh264 rpmfusion-free-updates rpmfusion-free copr:copr.fedorainfracloud.org:phracek:PyCharm google-chrome rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam updates fedora updates-archive
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2024-03-11T19:22:31Z solvables: 3
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2025-02-26T15:52:58Z solvables: 88
rpm-md repo 'rpmfusion-free' (cached); generated: 2024-10-27T07:49:25Z solvables: 347
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm' (cached); generated: 2024-12-16T12:28:59Z solvables: 10
rpm-md repo 'google-chrome' (cached); generated: 2025-02-28T22:19:17Z solvables: 4
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2025-02-26T15:36:10Z solvables: 17
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2025-02-06T20:28:34Z solvables: 2
rpm-md repo 'updates'; generated: 2025-03-01T01:15:47Z solvables: 21848
rpm-md repo 'fedora'; generated: 2024-10-24T13:55:59Z solvables: 76624
rpm-md repo 'updates-archive'; generated: 2025-03-01T01:55:19Z solvables: 35282
Resolving dependencies... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 571,2 MB (pkgcache branches: 0)
but the ārebaseā failed again:
error: While pulling fedora/41/x86_64/sericea: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/e4/aHFtCSIl1uy2rZBq_p6uPQLWwBl3uqxOusIPaiipQ.index: Server returned HTTP 502
Now the error 502 on rebase again,
but yesterday it almost succeeded:
$ rpm-ostree rebase fedora:fedora/40/x86_64/silverblue
ā Receiving objects; 99% (30859/30873) 1,7 MB/s 1,7 GB 3883 metadata, 26994 content objects fetched; 1681916 KiB transferred in 1001 seconds; 3,8 GB content written
Receiving objects; 99% (30859/30873) 1,7 MB/s 1,7 GB... done
Checking out tree 34acd1a... done
Inactive requests:
fedora-workstation-repositories (already provided by fedora-workstation-repositories-38-5.fc40.x86_64)
ffmpeg-free (already provided by ffmpeg-free-6.1.2-1.fc40.x86_64)
libva (already provided by libva-2.21.0-3.fc40.x86_64)
Enabled rpm-md repositories: updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree google-chrome copr:copr.fedorainfracloud.org:phracek:PyCharm rpmfusion-nonfree-steam rpmfusion-nonfree-nvidia-driver updates-archive
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'rpmfusion-free-updates'... done
error: Updating rpm-md repo 'rpmfusion-free-updates': Failed to download gpg key for repo 'rpmfusion-free-updates': Curl error (37): Could not read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-40 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-40]
Not sure if itās related, but still I wonder what I can do with itā¦
Seems to go thru now in germany. Was able to upgrade a new install now after having this issue.
baer@fedora:~$ sudo rpm-ostree upgrade
Receiving objects; 93% (8967/9571) 2,4 MB/s 378,0 MB
Receiving objects; 99% (13252/13268) 2,4 MB/s 503,1 MB
922 metadata, 12349 content objects fetched; 493716 KiB transferred in 210 seconds; 965,1 MB content written
Receiving objects; 99% (13252/13268) 2,4 MB/s 503,1 MB... done
Staging deployment... done
Upgraded:
whole lot of packages -> whole lot of packages
Run "systemctl reboot" to start a reboot
Went through here (Norway) as well, after a couple of retries:
martin@vger:~$ rpm-ostree upgrade
note: automatic updates (stage) are enabled
error: While pulling fedora/41/x86_64/kinoite: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/h5/8hWxkT1VqT+xvTyByyacZUAQ+I8PhN1wkAY1KRrNI.index: Server returned HTTP 502
martin@vger:~$ rpm-ostree upgrade
note: automatic updates (stage) are enabled
error: While pulling fedora/41/x86_64/kinoite: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/h5/8hWxkT1VqT+xvTyByyacZUAQ+I8PhN1wkAY1KRrNI.index: Server returned HTTP 502
martin@vger:~$ rpm-ostree upgrade
note: automatic updates (stage) are enabled
ā ¦ Receiving objects; 97% (7324/7499) 12.3 MB/s 418.5 MB
1696 metadata, 5854 content objects fetched; 428648 KiB transferred in 40 seconds; 820.7 MB content written
Receiving objects; 97% (7324/7499) 12.3 MB/s 418.5 MB... done
Checking out tree 879f215... done
...
Iām also having this same issue when attempting to update Kinoite and Iām in the Southern California area.
I got this error one time, then retried updating 2 seconds later, and got no error, updated successfully.
Still not working.
oh wait, so it might look like it went well even though there was an error?
now I donāt feel sure that my update went well earlier 
It went through earlier, later tries success rate 2 of 10. Think 3 days was fair game to wait out. Gone ahead and went back to regular workstation, need this laptop in production.
Peeps, while you have this problem, use this workaround to get updates
