There's 4 more rawhide updates in the same state: FEDORA-2022-3d1e3c4d1f, FEDORA-2022-fe9353b602, FEDORA-2022-3d66a8a606, FEDORA-2022-8acc519cb8.

There are a few updates in this status:
https://bodhi.fedoraproject.org/updates/?search=&status=pending&releases=F38&releases=F38C

I suppose some sort of outage of communication between Bodhi and Koji prevented these builds to be marked pending-signing.
Bodhi should automatically run a daily check and unstuck those builds after 2 days, so they may be pushed forward in the next 24h.

Some of those updates were still stuck after 5 days... that lead me to find a bug in Bodhi and I filed a PR to correct it, meanwhile I've manually unstuck all of those. The list should be clear now (the java update could take some time to be signed).

Hi @mattia,

can you elaborate on how you unstuck them? I usually tag/untag such builds with appropriate tags, to get things moving. But looking at the history of those builds included you probably did something in bodhi.

Hi @humaton ,
the update reported at first in the ticket and another one have been unstuck automatically by Bodhi periodic check.
For the other three I hacked them by using bodhi-shell in the bodhi-web pod on OC, but basically I just manually had bodhi signing the builds appropriately (f38-signing-pending) and let the things move on by their own.

These glitches happens when, for some reasons, bodhi processes a message about a build being tagged in a f-release-candidate where f is rawhide or other release with automatic updates enabled, but then it fails tagging the same build as pending-signing. You can see that by the fact the update is not marked as "signed" in the Metadata column.
There's a periodic task that checks those updates and fix them after two days (well 48h from the update creation + the time to reach 2:30 U.T. which is the time when the task is performed). The code was flawed, but it should be ok with the next bodhi release.

Thank you very much.