Bug 1339928 - Misleading error message on rebalance start when one of the glusterd instance is down
Summary: Misleading error message on rebalance start when one of the glusterd instance...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: hari gowtham
QA Contact:
URL:
Whiteboard:
Depends On: 1337899
Blocks: 1339923
TreeView+ depends on / blocked
 
Reported: 2016-05-26 08:27 UTC by hari gowtham
Modified: 2016-08-12 09:46 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.8.2
Clone Of: 1337899
Environment:
Last Closed: 2016-08-12 09:46:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description hari gowtham 2016-05-26 08:27:18 UTC
+++ This bug was initially created as a clone of Bug #1337899 +++

Description of problem:

While testing http://review.gluster.org/#/c/14347 I figured out that on a multi node cluster, if rebalance start is triggered with one of the glusterd instance been down which hosts one of the bricks, the failure message doesn't show the hostname.

root@54deb20dc641:/home/glusterfs# gluster v rebalance test-vol start
volume rebalance: test-vol: failed: Host node of brick /tmp/b1 is down

Also the message says that brick is down but glusterd is not.

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


How reproducible:
Always

Steps to Reproduce:
1. Create a multi node cluster
2. Create volume spanning over multiple nodes, start it
3. Trigger rebalance

Actual results:
Error message is misleading

Expected results:
Error message should be correct.

Additional info:

--- Additional comment from Vijay Bellur on 2016-05-23 02:58:36 EDT ---

REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node on error message of rebalance) posted (#1) for review on master by hari gowtham (hari.gowtham005)

--- Additional comment from Vijay Bellur on 2016-05-23 08:07:30 EDT ---

REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node details on error message of rebalance) posted (#2) for review on master by hari gowtham (hari.gowtham005)

--- Additional comment from Vijay Bellur on 2016-05-24 01:55:38 EDT ---

REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node details on error message of rebalance) posted (#3) for review on master by hari gowtham (hari.gowtham005)

--- Additional comment from Vijay Bellur on 2016-05-25 08:11:55 EDT ---

REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node details on error message of rebalance) posted (#4) for review on master by hari gowtham (hari.gowtham005)

--- Additional comment from Vijay Bellur on 2016-05-25 11:12:45 EDT ---

COMMIT: http://review.gluster.org/14495 committed in master by Atin Mukherjee (amukherj) 
------
commit fb57ac1acb228301edb98f2fe7cf93471363eb4a
Author: hari <hgowtham>
Date:   Mon May 23 12:07:21 2016 +0530

    Glusterd: printing the node details on error message of rebalance
    
    Problem: on the rebalance start with one of the glusterd being
    down among the volume, the error message says only about the
    brick path.
    
    Fix: adding the node details
    
    Change-Id: I5827d3a9a15b0461c9ce3a51c0b16246ca58f335
    BUG: 1337899
    Signed-off-by: hari <hgowtham>
    Reviewed-on: http://review.gluster.org/14495
    Tested-by: hari gowtham <hari.gowtham005>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 1 Vijay Bellur 2016-05-26 08:33:38 UTC
REVIEW: http://review.gluster.org/14541 (Glusterd: printing the node details on error message of rebalance) posted (#1) for review on release-3.8 by hari gowtham (hari.gowtham005)

Comment 2 Vijay Bellur 2016-07-15 06:08:05 UTC
REVIEW: http://review.gluster.org/14541 (Glusterd: printing the node details on error message of rebalance) posted (#2) for review on release-3.8 by hari gowtham (hari.gowtham005)

Comment 3 Vijay Bellur 2016-07-15 13:44:50 UTC
COMMIT: http://review.gluster.org/14541 committed in release-3.8 by Jeff Darcy (jdarcy) 
------
commit d407c1e6be61211799e3b0bc849134226dc35be7
Author: hari <hgowtham>
Date:   Mon May 23 12:07:21 2016 +0530

    Glusterd: printing the node details on error message of rebalance
    
            back-port of : http://review.gluster.org/#/c/14495
            back-port of : http://review.gluster.org/#/c/14540
    
    Problem: on the rebalance start with one of the glusterd being
    down among the volume, the error message says only about the
    brick path.
    
    Fix: adding the node details
    
    >Change-Id: I5827d3a9a15b0461c9ce3a51c0b16246ca58f335
    >BUG: 1337899
    >Signed-off-by: hari <hgowtham>
    
    >Change-Id: I3075f3a73e289dfe577742a3d5086531026f567d
    >BUG: 1339923
    >Signed-off-by: hari gowtham <hgowtham>
    
    Change-Id: Ic3988ff3042808d623642dc5a2ef82ef55ac8424
    BUG: 1339928
    Signed-off-by: hari gowtham <hgowtham>
    Reviewed-on: http://review.gluster.org/14541
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Tested-by: hari gowtham <hari.gowtham005>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal>
    Reviewed-by: Jeff Darcy <jdarcy>
    Smoke: Gluster Build System <jenkins.org>

Comment 4 Niels de Vos 2016-08-12 09:46:59 UTC
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.2, please open a new bug report.

glusterfs-3.8.2 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://www.gluster.org/pipermail/announce/2016-August/000058.html
[2] https://www.gluster.org/pipermail/gluster-users/


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