+++ This bug was initially created as a clone of Bug #2322468 +++ Description of problem: Fedora 42 has been released but registry.fedoraproject.org/fedora:latest is still Fedora 41. Version-Release number of selected component (if applicable): n/a How reproducible: Always Steps to Reproduce: 1. podman run --pull=always -ti --rm registry.fedoraproject.org/fedora:latest cat /etc/fedora-release Actual results: Fedora release 41 (Forty One) Expected results: Fedora release 42 (Forty Two) Additional info: This seems to happen on almost every Fedora release. Can we do something to make sure it doesn't?
it should be fixed automatically in a couple of hours, when the next nightly compose runs. The 20250515 compose ran at 7:15 UTC, before I updated the release source-of-truth used by cloud-image-uploader to mark F42 as stable, so the image uploader didn't apply the 'latest' tag when uploading that compose. It should do for the next compose.
Thanks, Adam. Is there any process change we could make so :latest gets updated at the same time as the Fedora release?
well, not *really*, no, because we don't time things so a Cloud compose is completing at the exact moment the release goes live, and the thing that syncs cloud images to registries (and updates the latest tag, if appropriate) runs when a compose completes. I mean, I guess we could add a manual step to the release SOP to do a manual registry edit to change the 'latest' tag to point to the most recent images for the new release, I guess, but we'd have to figure out the command(s) and credentials to use. It's not totally trivial since we're using multi-image manifests. We could *probably* just use skopeo to download the manifest for the fedora:42 (or whatever) tag and reupload it unmodified as fedora:latest , but I'm just whiteboarding there, I haven't tried it to see if there are any bear traps. It was enough of a pain writing the stuff to do it automatically.
there's a few ways we could have the uploader sync the compose done early on release day, potentially. the easiest is just to have someone update the fedfind metadata before that compose completes. it's not safe to update it before the bitflip, but I *think* it's safe to update it any time after the bitflip. I just usually update it when I wake up on release day because that's what I'm used to doing.
ugh. i wake up, and f41 is still latest (on quay.io and I presume r.f.o too). not sure why. will try and figure it out.
uf, right, there's a instance-level cache of the release metadata in fedfind which expires in one day. I forgot I wrote that. I *suspect* that maybe we got cached data where F41 was still 'current', when we published today's F42 containers. I kinda wanna leave it one more day and see if it gets it right next time.
ok, yeah, *now* it's right, latest points to 42. so, a combination of the timing of the metadata update, and the fedfind instance cache of that metadata. i'll see if I can come up with anything to improve this next time.
FEDORA-2026-be03969526 (fedfind-6.1.4-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-be03969526
FEDORA-2026-04f7655da7 (fedfind-6.1.4-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-04f7655da7
FEDORA-2026-be03969526 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-be03969526` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-be03969526 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-04f7655da7 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-04f7655da7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-04f7655da7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-be03969526 (fedfind-6.1.4-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-04f7655da7 (fedfind-6.1.4-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.