This is because IoT composes aren't really "Rawhide" composes. They're "43" composes. Compare:

• https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20250526.n.0/compose/metadata/composeinfo.json
• https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-43-20250527.0/compose/metadata/composeinfo.json

Note the Rawhide compose is called "Fedora-Rawhide-20250526.n.0" and its version is "Rawhide". The IoT compose is called "Fedora-IoT-43-20250527.0" and its version is "43".

The code in image-uploader looks like this:

        elif ffrel.release.lower() == "rawhide":
            tags.append("rawhide")

so we only update the tag called "rawhide" if the release's version is "rawhide" (or "Rawhide" or "RAWHIDE").

This is how Peter wanted the IoT composes to be, he wanted them to always have a number even when that number is the current Rawhide number. It causes quite a lot of problems like this.

I can send a PR to make image-uploader also update the 'rawhide' tag if the release number is the one fedfind thinks is the current Rawhide release number. That would affect any other similarly-versioned composes...I think updates composes are like this. I don't think it'd be a problem though.

https://pagure.io/cloud-image-uploader/pull-request/56 should fix this (and various other things).

PR #56 is deployed so it should be resolved with the next compose.

@siosm mentioned on the PR that maybe the same should be done for atomic desktops; it seems right to me with rawhide pointing to 43 and latest pointing to 42. @siosm, is there an example of where one of the repos isn't right?

The PR is not specific to IoT, it's just a generic logic change: we'll push to the 'rawhide' tag for any compose we're processing that is versioned with the current Rawhide release number (if we're pushing any images for it, of course).

I think IoT is the only compose like that, though. Atomic desktop images for Rawhide/current-43 come from the main "Fedora" Rawhide compose, which is versioned "Rawhide", so they should be working fine.

It looks good in the repo so thanks!

great. can someone close this then? Thanks!