Hello!
I noticed the other day that sigul was taking a while to sign all the builds on my ejabberd update. For a while, Bodhi thought two updates were signed and the rest were unsigned, and the Koji tags agreed. When I checked back later, it seemed that Koji thought all the builds were signed but Bodhi still listed them as unsigned. My guess is that bodhi-backend02 missed a few fedmsgs, but that's just speculation.
I've seen other builds get marked as signed successfully since then so I think things got back to normal, but I'm not sure what the procedure should be to get my ejabberd update in sync. I could manually edit the Bodhi database to just mark it signed, but I thought it'd be best to check with infra to see if there is a better procedure to follow for this case.
Eventually I plan to make the bodhi-push tool check with Koji to see if updates that it thinks aren't signed have been signed to solve the problem more generally:
https://github.com/fedora-infra/bodhi/issues/1781
The process we have been using for this case is to move the package from the fN-updates-testing-pending to fN-signing-pending. Then, autosign sees it again, and makes sure it's signed and puts it back in the right tag.
I'm not sure if we could automate this, but perhaps we could... just make bodhi put it back in the signing-pending tag anytime it saw something that was unsigned.
We could have bodhi do that move build, that sounds reasonable.
In the mean time, I discovered that I don't have permissions to do that operation myself for these builds:
$ koji move-build f27-updates-testing-pending f27-signing-pending ejabberd-18.01-1.fc27 ActionNotAllowed: tag requires autosign permission
Should someone do that for me, or should I just mark it signed in Bodhi's DB?
I've done this now. ;) Hopefully they will go out in the next push...
(well, it's signing kernels now, but it's in queue to be done)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks Kevin!
Metadata Update from @bowlofeggs: - Issue status updated to: Open (was: Closed)
Metadata Update from @bowlofeggs: - Issue status updated to: Closed (was: Open)
I filed https://pagure.io/pagure/issue/2927 about Pagure reopening this ticket when I said thanks.
@kevin would you expect the signing to take more than 15 hours? Most of the updates are still tagged f27-signing-pending. A couple two tree of them are marked f27-updates-testing-pending and Bodhi still doesn't think those are signed :/
f27-signing-pending
f27-updates-testing-pending
Login to comment on this ticket.