Bug 1285793

Summary:	Data Tiering: Change the error message when a detach-tier status is issued on a non-tier volume
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	tiering	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.7.6	CC:	bugs, byarlaga, dlambrig, nchilaka, sankarshan
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1284357	Environment:
Last Closed:	2016-04-19 07:49:12 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:	1236020, 1284357
Bug Blocks:	1245935, 1248337, 1260923

Comment 1 Vijay Bellur 2015-11-26 13:43:23 UTC

REVIEW: http://review.gluster.org/12766 (Tiering: change of error message for "v tier <vname>  detach status") posted (#1) for review on release-3.7 by hari gowtham (hari.gowtham005)

Comment 2 Vijay Bellur 2015-11-30 10:30:05 UTC

REVIEW: http://review.gluster.org/12766 (Tiering: change of error message for "v tier <vname>  detach status") posted (#2) for review on release-3.7 by hari gowtham (hari.gowtham005)

Comment 3 Vijay Bellur 2015-11-30 16:20:08 UTC

COMMIT: http://review.gluster.org/12766 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit d421c123952ed2059f816e92e57f5e07968cc778
Author: hari gowtham <hgowtham>
Date:   Mon Nov 23 11:58:52 2015 +0530

    Tiering: change of error message for "v tier <vname>  detach status"
    
            back port of : http://review.gluster.org/12713
    
    If the volume was not a tiered volume then empty status was being
    printed instead of an error message.
    
    >Change-Id: I13ccb16e1562966976a48d9365ced4c8a124de59
    >BUG: 1284357
    >Signed-off-by: hari gowtham <hgowtham>
    >Reviewed-on: http://review.gluster.org/12713
    >Tested-by: NetBSD Build System <jenkins.org>
    >Tested-by: Gluster Build System <jenkins.com>
    >Tested-by: Dan Lambright <dlambrig>
    >Reviewed-by: Dan Lambright <dlambrig>
    
    Change-Id: Ica4ed95844eab9a632eea8c35b686a4c1d73f78d
    BUG: 1285793
    Signed-off-by: Hari Gowtham <hgowtham>
    Reviewed-on: http://review.gluster.org/12766
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 4 Kaushal 2016-04-19 07:49:12 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.7.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user