Looks like currently builds for f35-updates-candidate are not auto-pushed to f35, stuck on f35-updates-candidate. Roughly ~70 builds (excluding LIve spin builds or so) are stuck on -candidate tag.
https://koji.fedoraproject.org/koji/builds?start=0&tagID=37073&order=-build_id&inherited=0&latest=1
Would you investigate this?
I think this affects CI as well as the last message from Bodhi was ~12 hours ago: https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.bodhi.update.status.testing.koji-build-group.build.complete&delta=180000
I think I have fixed this.
I made what we all thought was a cosmetic change to bodhi yesterday (to change the name from f35 to rawhide and the branch it expects to rawhide).
However, this seemed to reset the '--create-automatic-updates --not-composed-by-bodhi' settings on it, so bodhi stopped creating updates. ;(
Fixed that and retagged all the builds in this tag.
I'll leave this open while it signs and catches up to make sure nothing else is going wrong...
Metadata Update from @kevin: - Issue assigned to kevin - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: high-gain, high-trouble, ops
ok. I think it's processing back to normally.
Sorry for the troubles!
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks for the quick response @kevin :wink: Everything seems to be in order now.
Log in to comment on this ticket.