I don't see the build in stg repositories, and when I try to readd I see this:

doing a koji buildinfo on the nvr, I'm seeing it tagged on f30-infra-stg.
Do you still not see it?

I can see copr-backend-1.130-1.fc30 in dist repo too.

I don't see it here:
https://kojipkgs.fedoraproject.org/repos-dist/f30-infra-stg/latest/x86_64/pkglist

But I do see it here: https://kojipkgs.fedoraproject.org/repos-dist/f30-infra-stg/1311868/
Is the latest symlink pointing to 1311868 directory?

But I do see it here: https://kojipkgs.fedoraproject.org/repos-dist/f30-infra-stg/1311868/
Is the latest symlink pointing to 1311868 directory?

No.

lrwxrwxrwx. 1 apache apache 7 Dec  6 10:49 /mnt/fedora_koji_prod/koji/repos-dist/f30-infra-stg/latest -> 1311867

TBH, I used this script to flip 6 builds to staging:

1
2
3
4
5
6

#! /bin/sh

for build; do
    fedora_version=$(echo "$build" | sed 's/.*fc//')
    koji tag-build f$fedora_version-infra-candidate "$build"
done

Can I do this next time? This is not first time I am experiencing those issues.

So it looks like there is race condition.
Example sequence of events:

• build A is tagged
• dist-repo 1 starts generating
• build B is tagged
• dist-repo 2 starts generating
• dist-repo 2 finishes generating and is marked as latest
• dist-repo 1 finishes generating and is marked as latest

At the end dist-repo 1 is marked as latest, but it does not contain build B.

Yep. We already hit this with the coreos folks.

See: https://pagure.io/koji/issue/1630