Production and staging Koji instances have partially shared storage and kernel-4.16.10-200.fc27 build was deleted in production and its files were removed from fedora_koji netapp. Staging Koji still thinks the build exists, but fails to download it. A solution would be running staging Koji sync. I can do it, but after vacation.

@mizdebsk ah that makes sense. I don't have access to do that myself, but that solution sounds reasonable to me.

I also just realized that I may be able to just retag an older build I made in May as a workaround, so I am attempting that now. However, if you would like to do the sync go for it :)

I have been able to get my workaround to work as mentioned above, so this is not so critical for me now (though I suppose we do want to fix it for staging's sake).

One long-term solution for these kind of recurring problems would be automated or semi-automated, periodical Koji sync. I think that sync every 4 weeks (time builds are sitting in trashcan before being deleted) should be enough to avoid issues with deleted builds.

I just realized that @cverna is wanting to test Bodhi's container feature in staging, and @mohanboddu made some tag edits in staging Koji to support this. Thus, it may be ideal to hold off on resyncing Koji until @cverna's testing is complete.

@bowlofeggs's last comment is exactly why the prod-stg sync is kinda tricky: people testing stuff in staging.
That is why we need to sync up among the involved people for those.

I am planning to do staging Koji sync on August 16 or 17. If anyone has any objections, please let me know.

I'm starting the sync now.

The sync is done.