Bug 2359816 - rpm-ostree upgrade fails: cannot update repo 'updates-archive'
Summary: rpm-ostree upgrade fails: cannot update repo 'updates-archive'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm-ostree
Version: 41
Hardware: aarch64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Paul Whalen
QA Contact: Fedora Extras Quality Assurance
URL: https://fedoraproject-updates-archive...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-15 17:48 UTC by micha
Modified: 2025-04-16 00:14 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-04-15 18:54:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1593 0 None None None 2025-04-15 17:49:44 UTC

Description micha 2025-04-15 17:48:19 UTC
I tried to upgrade my fedora-iot installation on my aarch64 system today (stable branch) from F41 to F42 by running:

# 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>)

Reproducible: Always

Steps to Reproduce:
1.run rpm-ostree upgrade
Actual Results:
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>)

Expected Results:
Download works and upgrade (to F42) is done

Comment 1 Paul Whalen 2025-04-15 18:52:17 UTC
Thanks for your report, it looks specific to IoT- could you open an issue in our tracker: https://github.com/fedora-iot/iot-distro/issues

Comment 2 Dusty Mabe 2025-04-15 18:54:35 UTC
It's more an infra thing. Fixed with https://pagure.io/releng/archive-repo-manager/pull-request/26

Try again. The repo you are looking for was generated around 18:45:52 UTC today

Comment 3 micha 2025-04-15 21:13:31 UTC
(In reply to Dusty Mabe from comment #2)
> It's more an infra thing. Fixed with
> https://pagure.io/releng/archive-repo-manager/pull-request/26
> 
> Try again. The repo you are looking for was generated around 18:45:52 UTC
> today

Thank you.

I still get the same error hours later. I also tried `rpm-ostree refresh-md --force`.

Any tips on how to workaround this? I assume i get an outdated mirror or something like that?

Thank you

Comment 4 Dusty Mabe 2025-04-15 21:59:42 UTC
Maybe `sudo rpm-ostree cleanup --repomd` would help

Comment 5 micha 2025-04-15 22:18:00 UTC
(In reply to Dusty Mabe from comment #4)
> Maybe `sudo rpm-ostree cleanup --repomd` would help

I think this is just the longer-styled version of the command i already ran and referenced in the bug description that also did not help.

I'm still facing this issue.

Comment 6 Dusty Mabe 2025-04-15 23:14:17 UTC
I don't know then. Maybe some sort of CDN caching issue.

If you know you don't pull any packages from that repo then you can just disable it by editing /etc/yum.repos.d/fedora-updates-archive.repo

If you do pull packages from that repo you'll either need to wait for the CDN issue to resolve itself or open an infra ticket https://pagure.io/fedora-infrastructure/issues

Comment 7 micha 2025-04-16 00:14:16 UTC
(In reply to Dusty Mabe from comment #6)
> If you know you don't pull any packages from that repo then you can just
> disable it by editing /etc/yum.repos.d/fedora-updates-archive.repo

I'm not sure if my fedora-iot version pulled any packages from this repo. Is there a command to easily determine if this is the case?

> If you do pull packages from that repo you'll either need to wait for the
> CDN issue to resolve itself or open an infra ticket
> https://pagure.io/fedora-infrastructure/issues

Thanks. I opened https://pagure.io/fedora-infrastructure/issue/12497


Note You need to log in before you can comment on or make changes to this bug.