Bug #13017: Integrate upstream EPEL qpid with katello - Katello - Foreman

Actions

Copy link

Bug #13017

closed

Integrate upstream EPEL qpid with katello

Added by Justin Sherrill almost 9 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Justin Sherrill

Category:

Repositories

Target version:

Katello 3.1.0

Difficulty:

hard

Triaged:

Bugzilla link:

Pull request:

https://github.com/Katello/katello-packaging/pull/208, https://github.com/Katello/katello/pull/6198, https://github.com/Katello/katello-packaging/pull/252, https://github.com/Katello/katello-packaging/pull/253, https://github.com/Katello/katello-packaging/pull/269, https://github.com/Katello/katello-packaging/pull/270, https://github.com/Katello/katello-packaging/pull/272

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

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.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Justin Sherrill almost 9 years ago

http://pulp.readthedocs.org/en/latest/user-guide/installation.html#repositories
http://qpid.apache.org/packages.html

for upstream repos

Actions

Copy link

Updated by Brian Bouterse almost 9 years ago

I'm a Pulp developer who works closely with the Qpid team. I recommend switching to upstream Qpid packages. Pulp has already done this so you'll be aligned more closely with Pulp and Qpid, which would be good.

Actions

Copy link

Updated by Eric Helms almost 9 years ago

Category changed from 88 to 91

Actions

Copy link

Updated by Justin Sherrill over 8 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.

Actions

Copy link

Updated by Justin Sherrill over 8 years ago

Related to Bug #13268: [Katello 2.4] Capsule installer creates invalid qdrouterd.conf file which causes service to fail to start added

Actions

Copy link

Updated by Justin Sherrill over 8 years ago

Subject changed from Try to integrate upstream qpid with katello to Try to integrate upstream EPEL qpid with katello

Actions

Copy link

Updated by Eric Helms over 8 years ago

Translation missing: en.field_release changed from 86 to 144

Actions

Copy link

Updated by Eric Helms over 8 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:

https://fedorapeople.org/groups/katello/qpid_test/

Actions

Copy link

Updated by The Foreman Bot over 8 years ago

Status changed from New to Ready For Testing
Assignee set to Justin Sherrill
Pull request https://github.com/Katello/katello-packaging/pull/208 added

Actions

Copy link

#10

Updated by Tom Zven over 8 years ago

Hi Eric,
We were getting a lot of disconnects on qpid like this:

Apr 12 11:14:51 gitlab.hostname.net goferd¹³³³: [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
tfm-rubygem-qpid_messaging-0.34.1-7.git.112.05472c4.el7.centos.x86_64

rpm -qa |grep katello-rubygem
tfm-rubygem-katello-3.1.0-1.nightly.git.381.b47ca1f.el7.centos.noarch

Actions

Copy link

#11