Example: $ koji watch-task 28644925 Watching tasks (this may be safely interrupted)... 28644925 build (f29-binutils, /rpms/mame.git:ed5e2ca7746bae9042ed03640e8704d44023deca): open (buildhw-07.phx2.fedoraproject.org) 28645038 buildArch (mame-0.200-2.fc29.src.rpm, s390x): open (buildvm-s390x-03.s390.fedoraproject.org) 28645039 buildArch (mame-0.200-2.fc29.src.rpm, aarch64): open (buildvm-aarch64-13.arm.fedoraproject.org) 28645041 buildArch (mame-0.200-2.fc29.src.rpm, i686): open (buildvm-14.phx2.fedoraproject.org) 28645031 buildArch (mame-0.200-2.fc29.src.rpm, armv7hl): open (buildvm-armv7-15.arm.fedoraproject.org) 28645036 buildArch (mame-0.200-2.fc29.src.rpm, x86_64): open (buildvm-32.phx2.fedoraproject.org) 28644926 buildSRPMFromSCM (/rpms/mame.git:ed5e2ca7746bae9042ed03640e8704d44023deca): closed ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) This does not happen when running under Python 2. Seen with: koji-1.15.1-1.fc27.noarch python3-requests-2.18.4-2.fc27.noarch python3-urllib3-1.22-6.fc27.noarch python3-libs-3.6.5-1.fc27.x86_64 python3-pyOpenSSL-17.2.0-2.fc27.noarch
koji-1.16.1-2.fc30.noarch python3-requests-2.20.0-1.fc30.noarch
I'm seeing this on Fedora 29... Will new packages be built for it as well?
Me too.
https://github.com/fedora-infra/bodhi/issues/2870 may or may not be related, but Bodhi frequently gets an error from Koji under Python 3 that it did not get under Python 2. It's not the same error as this, however.
We've been having a very difficult time getting Bodhi to authenticate with Koji today, and I observed this same error message in Bodhi's logs to Koji. Thus, I think https://github.com/fedora-infra/bodhi/issues/2870 is related.
There is now an infrastructure ticket about this as well: https://pagure.io/fedora-infrastructure/issue/7458
I believe https://pagure.io/koji/pull-request/1203 should fix this.
I wonder if this is some variation on the keepalive race [1]. Or perhaps Fedora's hub really is just shutting down the connection due to load or something. I'm not sure why this would be py3 specific, but if it is a race, then odd things might tickle it. Have you adjusted your poll_interval config in koji.conf? If anyone can reliably reproduce this with --debug on, I'd be interested to see the full traceback.
Possible workaround: enable anon_retry in your koji.conf
Uh, Mike, did you see my pull request? I'm pretty sure I know what the problem is :)
Looking now. We had a mid-air collision
koji-1.16.1-3.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1fba27cd97
koji-1.16.1-3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f1d84fda6e
koji-1.16.1-3.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1fba27cd97
koji-1.16.1-3.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f1d84fda6e
koji-1.16.1-3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
koji-1.16.1-3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.