Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1337899

Summary:	Misleading error message on rebalance start when one of the glusterd instance is down
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	EasyFix, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1339923 1339928 (view as bug list)		Environment:
Last Closed:	2017-03-27 18:28:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1339923, 1339928

Description Atin Mukherjee 2016-05-20 12:00:21 UTC

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:

Comment 1 Vijay Bellur 2016-05-23 06:58:36 UTC

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)

Comment 2 Vijay Bellur 2016-05-23 12:07:30 UTC

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)

Comment 3 Vijay Bellur 2016-05-24 05:55:38 UTC

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)

Comment 4 Vijay Bellur 2016-05-25 12:11:55 UTC

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)

Comment 5 Vijay Bellur 2016-05-25 15:12:45 UTC

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 6 Shyamsundar 2017-03-27 18:28:06 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.9.0, please open a new bug report.

glusterfs-3.9.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/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/