I don't understand the current state of fedora-iot's ostree remote. I noticed when rpm-ostree upgrading to F42, podman got downgraded from 5.4.2 to 5.4.1. Even though http://packages.fedoraproject.org/pkgs/podman/podman/ shows the current version for F42 is 5.4.2 and this is also listed when running yum check-upgrade
yum check-upgrade
https://ostree.fedoraproject.org/iot/ returns 403
Since than, there are no new layers released when running rpm-ostree upgrade.
rpm-ostree upgrade
I found https://fedoraproject.org/wiki/Changes/CoreOSOstree2OCIUpdates but the quay.io repo for fedora-iot in tag 42 is also not updated since 18 days. https://quay.io/repository/fedora/fedora-iot?tab=tags (also wondering why this is not documented anywhere in case it's expected for fedora-iot users to rebase to quay.io repo).
What's going on? Why is fedora-iot so outdated now?
As you can see, after running rpm-ostree upgrade the latest version is now 6-7 days old already.
Deployments: ● fedora-iot:fedora/stable/aarch64/iot (index: 0) Version: 42.20250414.0 (2025-04-14T17:18:58Z) BaseCommit: abbf54c00c1095967346796c41254aef00d9c76e0c36553bddb78cd139889e9e ├─ repo-0 (2025-04-09T11:06:58Z) ├─ repo-1 (2025-04-14T16:46:21Z) └─ repo-2 (2025-04-09T14:21:07Z) Commit: 9a2a01f866281307ec623b4ad51abded60c24aefa1f3da2e0bfc56b85640b9c3 ├─ fedora (2025-04-11T05:17:06Z) ├─ fedora-cisco-openh264 (2024-08-21T16:04:02Z) ├─ mullvad-stable (2025-04-10T08:17:22Z) ├─ updates (2025-04-16T03:02:56Z) └─ updates-archive (2025-04-16T03:45:21Z) Staged: no StateRoot: fedora-iot GPGSignature: 1 signature Signature made Mon Apr 14 19:19:44 2025 using RSA key ID C8AC4916105EF944 Good signature from "Fedora <fedora-42-primary@fedoraproject.org>" LayeredPackages: bind-utils bluez ethtool hdparm htop iperf3 nc node-exporter systemd-container systemd-networkd tcpdump
So, it seems iot stable is still composing to f41?
CC: @pwhalen
Metadata Update from @james: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble
Metadata Update from @james: - Issue tagged with: ops
Adding @runcom as well :wave:
note, IoT does not compose that often - https://kojipkgs.fedoraproject.org/compose/iot/ . The three most recent composes for F42 were 20250410, 20250414 and 20250422. So until this morning, 20250414 was the most recent F42 IoT state.
The ostree is now updated (and will be daily). The containers should be fixed in the next couple of days. Apologies for any inconvenience.
Great. Closing this, let us know if there's anything we can do on our end.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.