Issue #3366: settings.yaml states the default broker to be Qpid but settings.py requires Rabbitmq - Pulp

Send by e-mail

Issue #3366

settings.yaml states the default broker to be Qpid but settings.py requires Rabbitmq

Added by milan over 2 years ago. Updated 12 days ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

milan

Category:

Installer

Sprint/Milestone:

3.0.0

Start date:

Due date:

Severity:

2. Medium

Version:

Platform Release:

3.0.0

Blocks Release:

OS:

Backwards Incompatible:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Easy Fix

QA Contact:

Complexity:

Smash Test:

Verified:

Verification Required:

Sprint:

Sprint 34

Description

Based on the Plugin Writer's Coding Workshop Feedback, specific things, Qpid vs Rabbitmq defaults confusion. The settings.yaml says we default to Qpid so folks install Qpid, but really in settings.py it's Rabbitmq. (this is a 1 line fix)

Associated revisions

Revision 33bb094d View on GitHub
Added by milan about 2 years ago

Refer to RabbitMQ as the default broker

Since Pulp still won't run with vanilla qpid broker[1] it seems reasonable to refer to the RabbitMQ as the default broker instead.

Fixes #3366 https://pulp.plan.io/issues/3366

[1] https://github.com/celery/kombu/pull/810

Revision 33bb094d View on GitHub
Added by milan about 2 years ago

Refer to RabbitMQ as the default broker

Since Pulp still won't run with vanilla qpid broker[1] it seems reasonable to refer to the RabbitMQ as the default broker instead.

Fixes #3366 https://pulp.plan.io/issues/3366

[1] https://github.com/celery/kombu/pull/810

History

#1 Updated by dalley over 2 years ago

Sprint/Milestone set to 54
Triaged changed from No to Yes

#2 Updated by milan over 2 years ago

Assignee set to milan

#3 Updated by milan over 2 years ago

see also: https://github.com/pulp/pulp/pull/3327

#4 Updated by milan over 2 years ago

Having switched the default "docstring" in the settings.yaml I wanted to try running development environment with RabbitMQ as a broker.
My deployment failed, hitting an epmd bug.
I just created a workaround patch[1] for the development environment so that folks can test Pulp3 without having to wait for an official fix.

[1] https://github.com/pulp/devel/pull/112