That's expected, koji garbage collects old logs and untagged builds and with the mass rebuild happening some time ago they would have been garbage collected, you'll just need to do a new scratch build to see the errors.

Yes, therefore the build logs are usually attached to the bug reports to keep them available.

Here is an example from an older mass rebuild with the build logs attached:
https://bugzilla.redhat.com/show_bug.cgi?id=1424434

Here is an example from an older mass rebuild with the build logs attached:

Sure, but it's likely a bit late for that now, what do you expect to happen? You've not stated anythign in this ticket other than they're lacking...

@till The problem was when we ran the script it was already late and some of the logs are gone. So, we had to tweak the script to just file the bugs but skip the logs part.

@pbrobinson I think the suggestion might be to make sure the script attaches the logs in the future, but it sounds like that might happen if I understand @mohanboddu's comment correctly (i.e., I'm assuming the "tweak" was not applied to the git copy of the script, and thus the next time we do one of these we'll see the logs?)

@pbrobinson I think the suggestion might be to make sure the script attaches the logs in the future, but it sounds like that might happen if I understand @mohanboddu's comment correctly (i.e., I'm assuming the "tweak" was not applied to the git copy of the script, and thus the next time we do one of these we'll see the logs?)

Yes, I wanted to make sure everyone knows that this problem existed. The tweak seems to just make sure that the script does not fail when there are no logs anymore, so I hope we are all set for the future.