[Bugs] [Bug 1219732] New: brick-op failure for glusterd command should log error message in cmd_history.log

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1219732

            Bug ID: 1219732
           Summary: brick-op failure for glusterd command should log error
                    message in cmd_history.log
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

In glusterd brick-op if underlying transport connection is broken between
glusterd and brick, then the command fails with a blank error message

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

How reproducible:
Always

Steps to Reproduce:
1.Create a volume & start it
2. Take the glusterd process in gdb and put a break point in
gd_syncop_submit_request () and continue
3. Stop the volume
3. the breakpoint will be hit, and set to ret to -1 after rpc_clnt_submit () is
executed

Actual results:
In cmd_history.log the command will be logged as failed with no error message

Expected results:
error message should be logged.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.