Issue #3366
closed
settings.yaml states the default broker to be Qpid but settings.py requires Rabbitmq
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)
Updated by dalley almost 7 years ago
- Sprint/Milestone set to 54
- Triaged changed from No to Yes
Updated by milan almost 7 years ago
see also: https://github.com/pulp/pulp/pull/3327
Updated by milan almost 7 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.
Updated by ipanova@redhat.com almost 7 years ago
- Status changed from NEW to POST
Updated by jortel@redhat.com almost 7 years ago
- Sprint changed from Sprint 33 to Sprint 34
Added by milan almost 7 years ago
Added by milan almost 7 years ago
Revision 33bb094d | View on GitHub
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.
Updated by milan almost 7 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp|33bb094deb0b56eefe59987972d05bdf3634cf87.
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by bmbouter over 4 years ago
- Category set to Installer - Moved to GitHub issues
- Tags deleted (
Pulp 3 installer)
.
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