Hi folks! So, you may have noticed that some package builds in Koji
recently are being reported as failed because the `tagBuild` task -
which happens at the end of a successful build - "failed". The error
reported is that the build was already tagged. This shouldn't be
happening - the builds definitely weren't tagged before the task ran.
We've been looking into it this morning and have filed an issue on Koji
for the devs to look into:
https://pagure.io/koji/issue/3220
So hopefully we'll be able to resolve it reasonably soon.
For package builds, this is ultimately only a cosmetic error. The tag
operation does actually work. The package build has effectively
completed successfully - the build was tagged and will be in future
composes. The task shows as failed in Koji, but you can ignore this.
For composes this is a bigger problem, as we're getting this error on
image builds (yes, these get tagged, no, I didn't know either!) and it
causes composes to fail if a blocking image hits this bug. We'll be re-
running composes that fail on this bug until it can be resolved.
Sorry for the trouble!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net