I built a batch of updates today, with the same contents for all F36, F35, and F34. The bodhi updates created from the F36 and F34 side tags were created fine, but the one for the new non-rawhide F35 seems to be broken. Builds have not been tagged with f35-signing-pending (which would match f36-signing-pending and f34-signing-pending, where the koji builds for the other two releases ended up), but with f35-build-side-44488-signing-pending, and they seem to be stuck there, preventing the bodhi update from getting pushed to stable.
f35-signing-pending
f36-signing-pending
f34-signing-pending
f35-build-side-44488-signing-pending
This is the stuck update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0047907574
This is the side-tag in question: f35-build-side-44488
Here's an example of a mis-tagged (?) koji build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1817132
It would be great to have this resolved soon, as I suspect this will affect any bodhi updates created from on-demand side-tags on f35 / branched. It's also not good to have this update stuck so long, as upstream is making regular releases and I'd rather not have f35 fall behind f34 and rawhide.
Never, I guess?
Bodhi updates for f35 stuck, possibly affecting all multi-build updates created from side-tags.
On further investigation, looks like signing on f35 is broken entirely: https://bodhi.fedoraproject.org/updates/?search=&releases=F35&rows_per_page=100 Looks like no builds made after ~16:30 UTC on Aug. 10 were signed.
Hi @decathorpe, this is expected. After the branching, we disable signing for f35 until we get rawhide compose out. Currently, rawhide compose is blocked by package signing(in progress).
Metadata Update from @mohanboddu: - Issue tagged with: low-gain, low-trouble, ops
Any ETA on this? I'm waiting for https://koji.fedoraproject.org/koji/buildinfo?buildID=1817458 to make it into the F35 build root. Thanks.
A branched compose is nearly finished... hopefully that will happen in the next hour or so... if it's successfull we will re-enable the flow.
We have a finished branched compose syncing out...
I have re-enabled the autosigning on f35 tags and retagged things so they should all be moving again.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I knew that branched updates were blocked until there's a successful compose, but I didn't realize that this was achieved by blocking signing, which is why I originally assumed this to be an unintentional problem. Sorry for the noise.