Actions
Issue #2112
closedStatus API does not log Qpid errors
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.9.0
Platform Release:
2.9.3
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
If the status API returns {'connected': False} the user knows there is an issue, but there is no other indication of the root cause. If an exception is encountered, I expect there to be some error level logging.
Actions
Adds logging for AMQP errors during /status/ API call
Previously errors were caught and not logged. This makes it very difficult to determine the root cause when an error is experienced.
https://pulp.plan.io/issues/2112 fixes #2112