I've briefly talked about this issue yesterday with @kevin who said that kojira seems to think that number of tasks exceeds the limit or something like this.
But today it started to happen again. rust-abomonation-0.7.3-1.fc31 is not in f31-build at least for 1.5 hours. I'm going to kick off newRepo manually for now every 20-30 minutes or so.
rust-abomonation-0.7.3-1.fc31
f31-build
kojira is running and it sees that f31-build repo needs regenerating:
Aug 06 07:56:46 koji02.phx2.fedoraproject.org kojira[28448]: 2019-08-06 07:56:46,319 [INFO] {28448} koji.repo.regen:616 Tag needs regen: f31-build
However it was stuck after failed XML-RPC call:
Aug 06 10:56:46 koji02.phx2.fedoraproject.org kojira[28448]: 2019-08-06 10:56:46,427 [INFO] {28448} koji:2572 Try #1 for call 46970 (listBuildroots) failed: 502 Server Error: Proxy Error
I've restarted the service and I will see if that helps.
Metadata Update from @mizdebsk: - Issue assigned to mizdebsk - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: koji
kojira is processing, but it is extremly slow due to slow Koji responses, which were also caught by Nagios monitoring.
Considering this as fixed - newRepo task for f31-build has been submitted by kojira:
Aug 06 12:20:35 koji02.phx2.fedoraproject.org kojira[5943]: 2019-08-06 12:20:35,099 [INFO] {5943} koji.repo.regen:720 Created newRepo task 36831572 for tag 6448 (f31-build), expired for 3277.5 sec
Metadata Update from @mizdebsk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.