Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1103354

Summary:	pulp.server.managers.event.remote requires qpid.messaging
Product:	[Retired] Pulp	Reporter:	Randy Barlow <rbarlow>
Component:	API/integration	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	medium	Docs Contact:
Priority:	low
Version:	Master	CC:	cduryee, cristi.falcas, mhrivnak, skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-28 22:09:29 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 Randy Barlow 2014-05-30 19:45:54 UTC

I noticed today that pulp.server.managers.event.remote has these two import statements:

 16 from qpid.messaging import Connection
 17 from qpid.messaging.exceptions import ConnectionError, MessagingError

I believe we should strive to be message broker agnostic as an upstream project, so we should not require qpid.messaging. Here are two suggested fixes:

1) It has been proposed that we could simply remove the feature provided by this module. It may not be very useful, especially since users can now monitor Celery tasks.

2) We could rework this module to use Kombu for message broker abstraction.

I would like to suggest that we make this low priority on 2.4. It's not a regression, since we didn't support rabbitmq in 2.3. It would be nice though since we are trying to allow users to choose rabbitmq for 2.4.

Comment 1 Randy Barlow 2014-11-20 13:26:49 UTC

I think this one is more of a defect than a task, since it is the only element of Pulp that actually does require a Qpid dependency. For Rabbit users this would be annoying.

It could be argued as a feature too I suppose since it's about supporting Rabbit with our event system.

Comment 2 Brian Bouterse 2015-02-28 22:09:29 UTC

Moved to https://pulp.plan.io/issues/443