Yeah, I was working on the same theory but our main test runner crashed before I could confirm it last night. I've added the F32 pki-base update to the 'workarounds' list for now and re-run the affected test for all affected updates, including this one, it's running or queued now.
Thanks to @cipherboy, we see that this is due to F32 beta freeze. So even though F32 pki update was created 11 days ago, it was already during the beta freeze period and it never was pushed to stable updates. The freeze period ended yesterday, thus pushing the update to stable. Now, 389-ds-base update was created before that happened, thus taking 'old' pki because that's the only set of packages available in F32.
We need to re-run tests on the 389-ds-base bodhi update.
I wasn't able to backport the patch because pagure wasn't letting anyone do anything over git (ssh). There are other regressions in this build. https://bugzilla.redhat.com/show_bug.cgi?id=1791342
I don't think this build should have been pushed to stable :-/