#39 Log a more useful message when a manifest arch is missing
Merged by jcline. Opened by adamwill.
adamwill/cloud-image-uploader missing-arch-better-log  into  main

When we don't publish a multi-arch manifest because an arch that's
present in the current published version of that manifest was not
present in the compose we're working on, the message we log
doesn't give you any indication which compose or manifest we were
working on, which makes it hard to debug the problem. Let's make
that better!

Signed-off-by: Adam Williamson awilliam@redhat.com

rebased onto 54de235d21c9e3a641a3a8dd9e8046b91331f05a

passes tests locally.

Pull-Request has been merged by jcline

Deployed this to production yesterday, here's what's failed so far:

[2024-12-03 03:09:44,724 fedora_image_uploader.handler ERROR] Arches ppc64le in current manifest registry.fedoraproject.org/fedora-silverblue:40 were not built in compose Fedora-40-updates-20241203.0, not publishing manifest
[2024-12-03 09:31:26,748 fedora_image_uploader.handler ERROR] Arches ppc64le in current manifest registry.fedoraproject.org/fedora-kinoite:42 were not built in compose Fedora-Rawhide-20241203.n.0, not publishing manifest

Cross-comparing with failed-composes, that actually looks like it's working as designed:
https://pagure.io/releng/failed-composes/issue/7496 has failed Silverblue ppc64le, https://pagure.io/releng/failed-composes/issue/7500 has failed Kinoite ppc64le. I guess we need to figure out why they're failing and fix them.

Okay, good. Given that, I'd like to drop the log level to warning since we can't do much beyond wait for a new compose and I'd like to only get emails when there's a problem on this end: https://pagure.io/cloud-image-uploader/pull-request/42

sure, works for me. hopefully @siosm can look into the failures.