Description of problem: When the SSH invocation in glusterfind fails, stderr from the other side is thrown away, so the user can't see the error. This is a regression introduced with commit feea851fad4f89b48bfe89fe3b75250cc7bd6501.
REVIEW: https://review.gluster.org/19761 (glusterfind: Log remote stderr on `node_cmd` error. Fixes #1559130) posted (#1) for review on master by Niklas Hambüchen
COMMIT: https://review.gluster.org/19761 committed in master by "Amar Tumballi" <amarts> with a commit message- glusterfind: Log remote stderr on `node_cmd` error. Fixes #1559130 The problem of lost stderr was introduced in commit feea851fad4f89b48bfe89fe3b75250cc7bd6501. Change-Id: Ic98f9bc9682ae3bd9c3ebea3855667fc8ba2843d BUG: 1559130 Signed-off-by: Niklas Hambüchen <mail>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/