Issue #1248: Base FileDistributor does not log errors, it only puts information about an error into the report for the user. - Pulp

Send by e-mail

Issue #1248

Base FileDistributor does not log errors, it only puts information about an error into the report for the user.

Added by bmbouter about 6 years ago. Updated about 1 year ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

bmbouter

Category:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

2.8.0

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

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.