Project

Profile

Help

Issue #398

closed

goferd doesn't log failures

Added by chris.a.st.pierre@gmail.com about 9 years ago. Updated over 4 years ago.

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

Description

Description of problem:

If goferd cannot authenticate to the parent, it fails silently unless you run it in the foreground.

Version-Release number of selected component (if applicable):

pulp-agent-2.3.1-1.el6.noarch
python-pulp-agent-lib-2.3.1-1.el6.noarch
gofer-0.77.1-1.el6.noarch
python-gofer-0.77.1-1.el6.noarch

How reproducible:

Always.

Steps to Reproduce:
1. Break authentication on the parent. I believe it should be sufficient to disable OAuth.
2. Start goferd on the child.
3. Be puzzled about why things aren't working.

Actual results:

goferd silently fails to authenticate and syncs time out with no explanation of why.

Expected results:

goferd should log the detailed and useful error message it produces when run in the foreground. (For extra points, a more useful message about where to look when a sync times out would be awful nice, too.)

Additional info:

+ This bug was cloned from Bugzilla Bug #1065367 +

Also available in: Atom PDF