Bug 1337908

Summary:	SAMBA+TIER : Wrong message display.On detach tier success the message reflects Tier command failed.
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	tiering	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.8.0	CC:	bugs, dlambrig, josferna, kaushal, kramdoss, nchilaka, rhinduja, rhs-smb, sashinde, vdas
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1328410	Environment:
Last Closed:	2016-06-16 14:07:54 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:	1322695, 1324439, 1328410
Bug Blocks:

Comment 1 Vijay Bellur 2016-05-20 12:31:16 UTC

REVIEW: http://review.gluster.org/14459 (tier/cli : printing a warning instead of skipping the node) posted (#1) for review on release-3.8 by hari gowtham (hari.gowtham005)

Comment 2 Vijay Bellur 2016-05-20 16:22:01 UTC

COMMIT: http://review.gluster.org/14459 committed in release-3.8 by Atin Mukherjee (amukherj) 
------
commit e931c0b9c4abf92ab4928ed3c16eb1d35144eec3
Author: hari gowtham <hgowtham>
Date:   Mon May 16 10:55:17 2016 +0530

    tier/cli : printing a warning instead of skipping the node
    
            back-port of : http://review.gluster.org/#/c/14347/8
    
    Problem: skipping the status of the nodes down creates confusion
    to the user as one might see the status as completed for all nodes
    and while performing detach commit, the operation will fail as the
    node is down
    
    Fix: Display a warning message
    
    Note: When the last node is down (as per the peer list) then
    warning message can't be displayed as the total number of peers
    participating in the transaction is considered to be the total count.
    
    >Change-Id: Ib7afbd1b26df3378e4d537db06f41f5c105ad86e
    >BUG: 1324439
    >Signed-off-by: hari gowtham <hgowtham>
    
    Change-Id: Id797bb45433c442f63b189ad16e0e95492a43721
    BUG: 1337908
    Signed-off-by: hari gowtham <hgowtham>
    Reviewed-on: http://review.gluster.org/14459
    Tested-by: hari gowtham <hari.gowtham005>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2016-06-16 14:07:54 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.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