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:
REVIEW: http://review.gluster.org/10659 (glusterd: populate errstr if gd_syncop_submit_request fails) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/10659 (glusterd: populate errstr if gd_syncop_submit_request fails) posted (#2) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/10659 committed in master by Vijay Bellur (vbellur) ------ commit 988db25572b94220a7cc69bcc3040c2a77b8e9a5 Author: Atin Mukherjee <amukherj> Date: Fri May 8 09:53:50 2015 +0530 glusterd: populate errstr if gd_syncop_submit_request fails Change-Id: Ie4a3edef5d553fc07de53b46f9485c46a4305245 BUG: 1219732 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/10659 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user