Actions
Issue #1248
closedBase FileDistributor does not log errors, it only puts information about an error into the report for the user.
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.8.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix, Pulp 2
Sprint:
Quarter:
Description
While working with the Puppet subclass of the platform's FileDistributor implementation I encountered an Exception, but the actual traceback of the exception wasn't in the logs. There was a small exception where the task logs that the publish experienced some kind of error, but the actual error traceback is not there. This is where I expected the error to be logged, but it was not.
I expected that the actual traceback would also be present in the logs, but all I saw was this:
pulp[10842]: pulp.server.controllers.repository:ERROR: (10842-98784) Exception caught from plugin during publish for repo [zoo-puppet]
pulp[10842]: pulp.server.controllers.repository:ERROR: (10842-98784) Traceback (most recent call last):
pulp[10842]: pulp.server.controllers.repository:ERROR: (10842-98784) File "/home/bmbouter/Documents/pulp/server/pulp/server/controllers/repository.py", line 784, in _do_publish
pulp[10842]: pulp.server.controllers.repository:ERROR: (10842-98784) distributor_id=dist_id
pulp[10842]: pulp.server.controllers.repository:ERROR: (10842-98784) PulpCodedException: The distributor asdf indicated a failed response when publishing repository zoo-puppet.
Actions
Adds error logging to platform base FileDistributor exceptions
Write the exception and its traceback to the log at error level when FileDistributor publish has an error.
https://pulp.plan.io/issues/1248 closes #1248