I try to build python-shpnix_rtd_theme in a side tag. The build is stuck in the waitrepo phase for over 40 minutes now. https://koji.fedoraproject.org/koji/taskinfo?taskID=124271907
I'd like the build to proceed.
Today, ideally.
kojira doesn't generate new repos for more than 2 hours. See: https://koji.fedoraproject.org/koji/tasks?state=all&view=tree&method=newRepo&order=-id
It is possibly related to this issue from yesterday. https://pagure.io/fedora-infrastructure/issue/12213
cross-referencing https://pagure.io/releng/issue/12371
Let me check if kojira is running.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, ops
I restarted kojira, let's see if the waitrepo will get unstuck now.
It seems that all the newRepo tasks are now processed.
@churchyard @ksurma Can you confirm that you are now unstuck?
Metadata Update from @zlopez: - Issue untagged with: Needs investigation - Issue assigned to zlopez - Issue tagged with: high-gain, low-trouble
Got confirmed by @ngompa that the restart of kojira helped.
Feel free to reopen the issue if there is still something.
Metadata Update from @zlopez: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Hi, @zlopez, thank you for unblocking this. I resubmitted the build to my side that and it's in the open state for 2,5 hours now. Is it because of the long queue? Is there another reason? Thank you in advance for looking at it. Link: https://koji.fedoraproject.org/koji/taskinfo?taskID=124273270
Metadata Update from @ksurma: - Issue status updated to: Open (was: Closed)
I tried koji free-task 124273384.
koji free-task 124273384
There were at least two issues:
There were 71 zuul llvm build tasks. (I freed these from s390x builders to allow other builds to happen)
There were a number of builders not checking in. (I fixed those so they are checking in again).
I think everything is back to working now. Please let me know if not.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.