I'm working on this.

https://pagure.io/cloud-image-uploader/pull-request/45

https://pagure.io/cloud-image-uploader/pull-request/45

This is now deployed to prod so things should be pushed more reliably for the more common architectures.

Looks like it worked. Kinoite failed in the latest F40 compose - https://pagure.io/releng/failed-composes/issue/7509 - and at https://quay.io/repository/fedora/fedora-kinoite?tab=tags we can see that, after that compose, the 40-x86_64 and 40-aarch64 tags were updated, the 40-ppc64le tag was not updated, but the 40 tag was updated even though ppc64le was missing.

Thanks, https://pagure.io/cloud-image-uploader/pull-request/45 is indeed an improvement.

The downside is that we now have a 41 tag that may or may not include all the architectures and thus can not be used reliably.

It would be nice if we could push the release tags with the latest builds that we have for all architectures in the registry, independently of their age, so that we always have all the architectures available for those tags.

yeah, I was thinking about something like that when I wrote it, it's probably doable somehow or other, but I've got about a zillion other things at the moment so I didn't have time to work it out. we probably need to adjust the whole flow so that we keep the info about the existing per-arch images when we do the initial check for 'missing' arches then use the existing hash or whatever for any 'missing' arch when constructing the multi-arch manifest later, blahblah handwave. I can try and get to it sometime, if you get to it first, go for it.