#1192 Frequent connection aborted errors when the Koji client is run under Python 3
Closed: Fixed 11 months ago by mikem. Opened a year ago by bowlofeggs.

I frequently see the Koji client exit with the error message ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) when running tasks that watch things in Koji, such as koji build, koji watch-logs, or koji watch-task. These errors seem to coincide with the Koji client switching to Python 3, though I am not sure.

This was originally reported in rhbz#1609298.


Hey koji folks. Lots of folks are seeing this now.

I do not know if this is a koji bug, a python3 bug or a infrastructure config bug, some advise would be welcome.

It's been filed in at least:

https://bugzilla.redhat.com/show_bug.cgi?id=1609298
https://pagure.io/fedora-infrastructure/issue/7486
https://pagure.io/releng/issue/7738

and noted on the devel list a few times. Anything we can do to get more info? (I have a debug output on the releng issue).

I kinda suspect this is related to is_conn_error in koji/__init__.py. Note that there's some exception handling logic in _sendCall which can be summarized as: "if is_conn_error() says this is a connection error, debug log a 'Connection Error' message and restart the session; otherwise, just go ahead and raise the exception". That sounds very very much like what we're running into here, to me. So I suspect that, in some circumstance, is_conn_error() is returning True on Python 2 but False on Python 3.

I believe I figured it out. https://pagure.io/koji/pull-request/1203 should - I hope - fix this. I've been testing it locally and haven't had a watch-task die on me yet.

Commit 1b63828 fixes this issue

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.17

8 months ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #1203 Merged 11 months ago