Actions
Issue #2112
closed
Status 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.
Updated by bmbouter over 7 years ago
PR available at: https://github.com/pulp/pulp/pull/2660
Updated by semyers over 7 years ago
- Version set to 2.9.0
- Platform Release deleted (
2.9.2)
Added by bmbouter over 7 years ago
Added by bmbouter over 7 years ago
Revision 13e64ce6 | View on GitHub
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.
Updated by bmbouter over 7 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|13e64ce6d106403973989d3cc7b4e5f9fc471043.
Updated by semyers over 7 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
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