Bug 1305868 - [USS]: Need defined rules for snapshot-directory, setting to a/b works but in linux a/b is b is subdirectory of a
Summary: [USS]: Need defined rules for snapshot-directory, setting to a/b works but in...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: 3.7.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard: USS
Depends On: 1163736 1168819 1304282
Blocks: 1166590
TreeView+ depends on / blocked
 
Reported: 2016-02-09 12:37 UTC by Vijaikumar Mallikarjuna
Modified: 2016-04-19 07:25 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.7.9
Doc Type: Bug Fix
Doc Text:
Clone Of: 1168819
Environment:
Last Closed: 2016-04-19 07:25:16 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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@redhat.com)

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@redhat.com)

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@redhat.com) 
------
commit fa3df1f5eaf3104c0eb597b954dd17b1a067db8c
Author: vmallika <vmallika@redhat.com>
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@redhat.com>
    > Reviewed-on: http://review.gluster.org/9209
    > Smoke: Gluster Build System <jenkins@build.gluster.com>
    > Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    > Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    > Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    > NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    
    Change-Id: I1b85d6851a223b51714c0498b457c41db99f5f58
    BUG: 1305868
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13409
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

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


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