Integrate upstream EPEL qpid with katello
We should try to integrate the upstream versions of all the qpid packges on el6 & 7.
I've seen errors on them, but unsure what the issue was. Needs investigating.
Refs #13017 - cleanup qpid from comps
some qpid packages are still required, but since
they are only dispatch router related moving those
to katello repo
#1 Updated by Justin Sherrill over 3 years ago
#4 Updated by Justin Sherrill about 3 years ago
After an extensive discussion with the qpid community, we will need to wait for their next release of qpid in epel due to a couple issues:
1. existence of a bug where dispatch router and qpid fail to communicate
2. dispatch router mistakenly runs as the qpidd user.
We plan to move to the new epel packages within a couple weeks when they land and these issues should be solved.
#8 Updated by Eric Helms about 3 years ago
I created a little repo with qpid_messaging gem and katello master as of this date built against the EPEL qpid packages if anyone wants to help test and debug issues:
#10 Updated by Tom Zven about 3 years ago
We were getting a lot of disconnects on qpid like this:
Apr 12 11:14:51 gitlab.hostname.net goferd1333: [ERROR][pulp.agent.eae1cdfe-382d-43f4-97ba-d6c378c4e72d] gofer.messaging.adapter.proton.reliability:53 - Connection amqps://foreman.hostname.net:5647 disconnected
Now we updated to qpid 0.34 from EPEL and the packages you've published on the test repo and It seems to work fine. No errors or disconnect for 2 days now.
rpm -qa |grep messaging
rpm -qa |grep katello-rubygem
#17 Updated by Justin Sherrill almost 3 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello-packaging|4b636fde3823c4200367498e1062a7531ebcca38.