python-kombu is newer on fedora23, so fedora23 is missing several bugfixes that our patches fix
In F23, you'll receive 3.0.26-2. This will still run with pulp, but there are a few bugfixes that you may be missing. I'm not sure exactly which ones. To fix the we would need to upgrade to something newer than 3.0.26-2 + patches. If we are going to upgrade, the best thing would be to upgrade to the unreleased 3.0.30 after we test pulp against it. We can ship that with future pulp releases that need to run on f23.
This issue could be purposed to track switching python-kombu to 3.0.30 for F23+
#2 Updated by semyers over 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to semyers
I was poking around a little bit, and here's what I've found: 3.0.32 is available on PyPI, but none of our patches apply cleanly against it. Many hunks apply cleanly in reverse, but not all, indicating that they've already been applied. The hunks that don't reverse cleanly, however, could have failed for any number of reasons. The easy solution is to strip out all the patches, but I don't feel familiar enough with them to make that call.
Another issue (and, if we're happy to bump up to kombu 3.0.32, it should literally be another issue) is that kombu 3.0.30+ requires python-amqp >= 1.4.7. We build 1.4.6 in our deps, 1.4.7 is available in fedora updates-testing for fc23, and the latest on PyPI is 1.4.8.
That all said, I built kombu 3.0.32 and amqp 1.4.8 rpms using the latest tarballs from PyPI. pulp master and gofer 2.7 tests all passed, so I'll put together a PR and see what happens. :)
#4 Updated by semyers over 5 years ago
amqp 1.4.7 also satisfies the requirements for kombu 3.0.32, and has the bonus of being in fedora already, so we got that built on Friday, tested it, and bumped the external deps. This ticket, then, can focus back on upgrading python-kombu.
I manually tested with our spec of python-kombu, modified to apply no patches, and I also tested with the fedora spec of python-kombu, all updated to 3.0.32. All testing was done in a fedora 23 vagrant env.
Here's what I tested:
- Pulp can reconnect to the broker if the broker goes down while pulp is running
- Pulp can connect to the broker is the broker is started after pulp starts
- No ugly exceptions are raised by kombu when pulp is stopped (pstop; watch console and journal)
- ConnectionError is correctly replaced with AuthenticationFailure when authn to qpidd fails
All tests passed.
I also checked that some code clean up file descriptors was in place (it is), and that it has some deadlock prevention code (it isn't).
Overall, 3.0.32 looks good. The deadlock prevention code has been applied to kombu's 3.0 branch, and should be present in kombu 3.0.33 when it's released.
#11 Updated by bmbouter over 5 years ago
Upstream kombu has been released, but now depends on amqp 1.4.9.
#12 Updated by semyers over 5 years ago
amqp 1.4.9 and kombu 3.0.33 are now in rawhide, and will be in fedora 24. There are a few options, but I'm not quite sure how to proceed with regard to fedora23 and the packages we build.
Please register to edit this issue