I was redirected here from: https://bugzilla.redhat.com/show_bug.cgi?id=2359816#c6
When i run rpm-ostree upgrade, i get a download error for updates-archive which prevent me from upgrading to F42.
rpm-ostree upgrade
# rpm-ostree status State: idle Deployments: ● fedora-iot:fedora/stable/aarch64/iot Version: 41.20250411.0 (2025-04-11T12:09:55Z) BaseCommit: b914c5cb58c6b1b75ef36f35ec0874b8db16cb84da56926a48af9784068ca617 GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1 LayeredPackages: bind-utils bluez ethtool hdparm htop iperf3 nc node-exporter systemd-container systemd-networkd tcpdump
# rpm-ostree cleanup -m # rpm-ostree upgrade 2 metadata, 0 content objects fetched; 788 B transferred in 6 seconds; 0 bytes content written Checking out tree abbf54c... done Enabled rpm-md repositories: updates fedora-cisco-openh264 fedora mullvad-stable updates-archive Updating metadata for 'updates'... done Updating metadata for 'fedora-cisco-openh264'... done Updating metadata for 'fedora'... done Updating metadata for 'mullvad-stable'... done Updating metadata for 'updates-archive'... done error: Updating rpm-md repo 'updates-archive': cannot update repo 'updates-archive': Yum repo downloading error: Downloading error(s): repodata/69a3730a283b85a4b3cff7d04bfde3b2b234f0607ebc17319d7a8d143a8e066e-primary.xml.zst - Cannot download, all mirrors were already tried without success; Last error: Status code: 403 for https://fedoraproject-updates-archive.fedoraproject.org/fedora/42/aarch64/repodata/69a3730a283b85a4b3cff7d04bfde3b2b234f0607ebc17319d7a8d143a8e066e-primary.xml.zst (IP: <redacted IPv6 address>)
I already tried rpm-ostree cleanup -m and rpm-ostree refresh-md --force and also waiting for a couple of hours (at least 5-6), neither which helped me to solve the problem.
rpm-ostree cleanup -m
rpm-ostree refresh-md --force
2025/05/01 I don't need this done at any specific date as it's a non-critical system and i can be patient, however, i would love to update to F42 as soon as possible :)
CC: @dustymabe
Yeah I sent them here. I can’t reproduce the issue and the only way I can explain it is some CDN caching issue. Do we have cloud front configured for this URL?
Yes, it looks like cloudfront:
;; QUESTION SECTION: ;fedoraproject-updates-archive.fedoraproject.org. IN A ;; ANSWER SECTION: fedoraproject-updates-archive.fedoraproject.org. 197 IN CNAME d1mexvma47kc2l.cloudfront.net.
Btw, when i open the URL in the Browser, i get this XML response:
<Error> <Code>AccessDenied</Code> <Message>Access Denied</Message> <RequestId>598RGXSTTD3EJR4Q</RequestId> <HostId> XpS9QRTDgr/Lk07RlD+s9KsOE5v7Qce2n2KmCh+kNMkxQTa3h9QMqnigd3Kw6W1XvJPOsMEtFdjFW38W3Cz52w== </HostId> </Error>
(values change with each reload) Maybe that helps debugging inside cloudfront tools.
(Problem still exists)
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
ok, the s3 bucket did not have public access.
I am not sure why that was the case. I didn't change it...
I added public list/read access. Can you confirm it's working now?
Metadata Update from @kevin: - Issue assigned to kevin
Can you confirm it's working now?
Yes! It work's! Thank you so much.
Metadata Update from @breiti: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.