Once we receive fedmsg that koji build is complete, we trigger rpmlint which downloads rpms and then checks them. However with the texlive package (or maybe even with others as well), koji says there are 0 rpms in the build.
rpmlint
texlive
Logs (disregard the traceback): https://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/208799/steps/runtask/logs/taskotron-stdio.log https://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/208799
The line that is important is: [libtaskotron] 13:59:43 INFO Fetching 0 RPMs for: texlive-2015-25.20150728_r37987.fc25 (into /var/tmp/taskotron/root/task-Q0ICEX)
[libtaskotron] 13:59:43 INFO Fetching 0 RPMs for: texlive-2015-25.20150728_r37987.fc25 (into /var/tmp/taskotron/root/task-Q0ICEX)
However if I run it manually afterwards I get: [libtaskotron] 09:54:22 INFO Fetching 5732 RPMs for: texlive-2015-25.20150728_r37987.fc25 (into /var/tmp/taskotron/mkrizek/task-XJBnz3)
[libtaskotron] 09:54:22 INFO Fetching 5732 RPMs for: texlive-2015-25.20150728_r37987.fc25 (into /var/tmp/taskotron/mkrizek/task-XJBnz3)
It seems like that something in koji is done in incorrect order like fedmsg about build completion is send before rpms are made available perhaps? The problem here is most likely related to the number of rpms in the build (5732 in the case of texlive is a lot), because it works well with all other builds.
Investigate and propose a fix.
This ticket is a duplicate of https://pagure.io/taskotron/libtaskotron/issue/344
Seems to be happening consistently for texlive. Another crash here: https://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/214813/steps/runtask/logs/stdio Please notice:
[libtaskotron] 19:22:13 INFO Fetching 0 RPMs for: texlive-2015-26.20150728_r37987.fc25 (into /var/tmp/taskotron/root/task-HMoT2f)
! In #776#10907, @kparal wrote: Seems to be happening consistently for texlive. Another crash here: https://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/214813/steps/runtask/logs/stdio Please notice: [libtaskotron] 19:22:13 INFO Fetching 0 RPMs for: texlive-2015-26.20150728_r37987.fc25 (into /var/tmp/taskotron/root/task-HMoT2f)
For a record, there was a new tb though, it has been reported in a separate ticket: #792
I have created a Koji ticket here: https://fedorahosted.org/koji/ticket/331
If there's no response, we'll need to get hold of [[ https://admin.fedoraproject.org/accounts/user/view/mikem | mikem ]].
Just a note, this happened for another package: http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/172861 http://taskotron.stg.fedoraproject.org/taskmaster/builders/x86_64/builds/271187 http://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/225338
Has there been any update on this? It sounds like the koji folks aren't using trac anymore and have moved to pagure but I don't see the ticket above in pagure
I spoke to mikem during Flock, he said he would look into that. But I have no update about that. I asked again in the ticket (also about pagure).
The Koji problem was supposedly fixed, but it will need adjustments in fedmsg plugin as well: https://pagure.io/fedora-infrastructure/issue/5546
@ralph made the fedmsg plugin adjustments and we're just waiting to be deployed to production (hopefully in a matter of a few days)
New koji and fedmsg plugin has been deployed. We should no longer need the docker workaround, and texlive and other rpms should start working. The easiest way to confirm this is probably to wait for a new texlive build.
I have inspected latest texlive builds and it seems this finally works! The very latest build failed due to our DNS issues, but the builds before that seems to have worked fine: http://taskotron-dev.fedoraproject.org/resultsdb/results/9420418 http://taskotron-dev.fedoraproject.org/resultsdb/results/9570513 http://taskotron-dev.fedoraproject.org/resultsdb/results/9573220 http://taskotron-dev.fedoraproject.org/resultsdb/results/9646706
Closing. Please reopen if you see another Fetching 0 RPMs message.
Fetching 0 RPMs
Login to comment on this ticket.