Project

Profile

Help

Issue #2339

closed

httpd fails to start if AMQP bus for consumers is unavailable

Added by Ichimonji10 over 7 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Pulp has two AMQP messaging buses: one for its task management system, and another for consumers. The former is mandatory for Pulp to function, and the latter is optional. Unfortunately, httpd will not start if the consumer messaging bus is unavailable.

To demonstrate this issue, edit /etc/pulp/server.conf, edit the [messaging] section, and reference an unavailable transport. For example, try this:

[messaging]
# transport: qpid
transport: foo

Then, restart httpd. httpd will fail to start. It seems strange that httpd will not start when this optional messaging bus cannot be contacted.

This issue is especially likely to bite a user if they are attempting to switch from qpid to rabbitmq.

Also available in: Atom PDF