Bug 963628 - glusterd : 'gluster volume create <vol_name> [bricks]...' is not giving detailed error message if bricks are not part of RHS node from where command is executed, it just says 'volume create: <vol_name>: failed'
glusterd : 'gluster volume create <vol_name> [bricks]...' is not giving detai...
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Krutika Dhananjay
Depends On: 960390
  Show dependency treegraph
Reported: 2013-05-16 05:44 EDT by Krutika Dhananjay
Modified: 2013-07-24 13:37 EDT (History)
6 users (show)

See Also:
Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 960390
Last Closed: 2013-07-24 13:37:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 1 Anand Avati 2013-05-16 05:49:01 EDT
REVIEW: http://review.gluster.org/5018 (glusterd: Set op_errstr to error string received from peer) posted (#1) for review on master by Krutika Dhananjay (kdhananj@redhat.com)
Comment 2 Krutika Dhananjay 2013-05-16 05:50:00 EDT
http://review.gluster.org/#/c/5018/ <--- Patch posted for review.
Comment 3 Anand Avati 2013-05-16 22:27:56 EDT
COMMIT: http://review.gluster.org/5018 committed in master by Vijay Bellur (vbellur@redhat.com) 
commit 5780e274c78aab671e5fb72d66fec23f90576e51
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 16 15:05:09 2013 +0530

    glusterd: Set op_errstr to error string received from peer
    ... in case of volume op failure on remote host
    Change-Id: I7177dc02369dffa82f217496559532d18b7c7c7a
    BUG: 963628
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/5018
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

Note You need to log in before you can comment on or make changes to this bug.