Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1609298
Summary: | koji: When running under Python 3, wait-* commands will not wait indefinitely | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Florian Weimer <fweimer> |
Component: | koji | Assignee: | Mike McLean <mikem> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | awilliam, dennis, hobbes1069, jkeating, mikem, projects.rg, pzhukov, rbarlow, rharwood, rjones, swt, thofmann, vondruch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | koji-1.16.1-3.fc29 koji-1.16.1-3.fc28 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-13 02:31:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Florian Weimer
2018-07-27 13:32:43 UTC
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. |