Bug 1771895 - geo-rep: Improve debugging in log_raise_exception
Summary: geo-rep: Improve debugging in log_raise_exception
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-13 08:25 UTC by Kotresh HR
Modified: 2019-11-13 12:17 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-13 12:17:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23707 0 None Merged geo-rep: Improve debugging 2019-11-13 12:17:30 UTC

Description Kotresh HR 2019-11-13 08:25:19 UTC 
Description of problem:
When gsyncd failed with tracebacks during start, it prints
only exception object but not the error string. This patch
adds the error string as well.
    
Version-Release number of selected component (if applicable):
mainline

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Example error message
"failed with ImportError"
    


Expected results:
"failed with ImportError: No module named _io."


Additional info:
Comment 1 Worker Ant 2019-11-13 08:27:48 UTC 
REVIEW: https://review.gluster.org/23707 (geo-rep: Improve debugging) posted (#1) for review on master by Kotresh HR
Comment 2 Worker Ant 2019-11-13 12:17:31 UTC 
REVIEW: https://review.gluster.org/23707 (geo-rep: Improve debugging) merged (#2) on master by Sunny Kumar
Note You need to log in before you can comment on or make changes to this bug.