This was manually untagged from f37 by @kevin :

$ koji list-history --build=openssl-pkcs11-0.4.12-2.fc37
Mon Aug  8 11:35:39 2022 openssl-pkcs11-0.4.12-2.fc37 tagged into f37-updates-candidate by jjelen
Mon Aug  8 11:35:49 2022 openssl-pkcs11-0.4.12-2.fc37 tagged into f37-signing-pending by bodhi
Mon Aug  8 11:36:01 2022 openssl-pkcs11-0.4.12-2.fc37 untagged from f37-signing-pending by autopen
Mon Aug  8 11:36:01 2022 openssl-pkcs11-0.4.12-2.fc37 tagged into f37-updates-testing-pending by autopen
Mon Aug  8 11:37:15 2022 openssl-pkcs11-0.4.12-2.fc37 untagged from f37-updates-testing-pending by bodhi
Mon Aug  8 11:37:17 2022 openssl-pkcs11-0.4.12-2.fc37 untagged from f37-updates-candidate by bodhi
Mon Aug  8 11:37:20 2022 openssl-pkcs11-0.4.12-2.fc37 tagged into f37 by bodhi
Mon Aug  8 11:37:31 2022 openssl-pkcs11-0.4.12-2.fc37 tagged into eln by distrobuildsync-eln/jenkins-continuous-infra.apps.ci.centos.org [still active]
Tue Aug  9 20:01:19 2022 openssl-pkcs11-0.4.12-2.fc37 tagged into f38 by humaton [still active]
Thu Aug 11 19:23:10 2022 openssl-pkcs11-0.4.12-2.fc37 untagged from f37 by kevin

there may be some reason for this.

It was built before branching, but the f37 one was untagged due to https://bugzilla.redhat.com/show_bug.cgi?id=2117859 (which was a beta blocker). So it was untagged to unblock f37.

So, we can't tag it back in without blocking final there and I think it's still being worked on...

Closing this now, but if there's further action feel free to re-open!

Well we have an issue that both f36 and f38 is newer than f37 so something should be done, I can't believe it's just broken in f37, or working in the other 2 if broken in f37. But meh

Yeah, I am not sure if it's not broken in rawhide or we just are ignoring that for now?

CC: @adamwill

Oh, I think we can tag it back into F37 now, sorry for not remembering this. The related cluster of bugs seems to have been finally cleared up by https://bodhi.fedoraproject.org/updates/FEDORA-2022-cbcb55d5c7 .

This is why we should find a way to keep track of things we have untagged, I guess...

@pbrobinson it was broken in F37 and Rawhide but not F36, because F36 had an older bind that didn't expose the problem. By the time we found the bug, the -2 build had already been in a Rawhide compose, so we couldn't untag it from Rawhide. But it hadn't yet made F37, so we could (and did) untag it from F37.

ok. I re-tagged it in.

Note that we can untag from rawhide now if we think it's worth doing. :)