Bug 1305868

Summary:	[USS]: Need defined rules for snapshot-directory, setting to a/b works but in linux a/b is b is subdirectory of a
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	snapshot	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.7	CC:	bugs, rhinduja, rjoseph, smohan, surs, vmallika
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	USS
Fixed In Version:	glusterfs-3.7.9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1168819	Environment:
Last Closed:	2016-04-19 07:25:16 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:	1163736, 1168819, 1304282
Bug Blocks:	1166590

Comment 1 Vijay Bellur 2016-02-09 12:43:58 UTC

REVIEW: http://review.gluster.org/13409 (uss: validate USS option features.snapshot-directory) posted (#1) for review on release-3.7 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Vijay Bellur 2016-02-09 12:44:40 UTC

REVIEW: http://review.gluster.org/13409 (uss: validate USS option features.snapshot-directory) posted (#2) for review on release-3.7 by Vijaikumar Mallikarjuna (vmallika)

Comment 3 Vijay Bellur 2016-02-15 08:24:38 UTC

COMMIT: http://review.gluster.org/13409 committed in release-3.7 by Rajesh Joseph (rjoseph) 
------
commit fa3df1f5eaf3104c0eb597b954dd17b1a067db8c
Author: vmallika <vmallika>
Date:   Tue Feb 9 18:11:24 2016 +0530

    uss: validate USS option features.snapshot-directory
    
    This is a backport of http://review.gluster.org/#/c/9209
    
    USS option features.snapshot-directory
       contains only 'alphanum, -, _, .'
       starts with dot (.)
       value cannot exceed 255 characters
    and throws error for any other argument.
    
    > Change-Id: Iad64635206ddf5599351020d99aafb3dd9d17bc1
    > BUG: 1168819
    > Signed-off-by: vmallika <vmallika>
    > Reviewed-on: http://review.gluster.org/9209
    > Smoke: Gluster Build System <jenkins.com>
    > Reviewed-by: Avra Sengupta <asengupt>
    > Reviewed-by: Manikandan Selvaganesh <mselvaga>
    > Reviewed-by: Rajesh Joseph <rjoseph>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.com>
    
    Change-Id: I1b85d6851a223b51714c0498b457c41db99f5f58
    BUG: 1305868
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/13409
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>

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

glusterfs-3.7.9 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-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user