Bug 1135691

Summary: [barrier] features.barrier should be a NO_DOC option
Product: [Community] GlusterFS Reporter: Atin Mukherjee <amukherj>
Component: coreAssignee: Atin Mukherjee <amukherj>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-bugs, sasundar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-14 17:27:27 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:

Description Atin Mukherjee 2014-08-30 12:01:41 UTC
Description of problem:

Since snapshot commands would internally trigger barrier brick op, barrier option should not be exposed to the customer and should have NO_DOC doctype.

Comment 1 Anand Avati 2014-08-30 12:34:54 UTC
REVIEW: http://review.gluster.org/8572 (barrier: features.barrier should be a NO_DOC) posted (#1) for review on master by Atin Mukherjee (amukherj)

Comment 2 Anand Avati 2014-08-30 12:46:21 UTC
REVIEW: http://review.gluster.org/8572 (barrier: features.barrier should be a NO_DOC) posted (#2) for review on master by Atin Mukherjee (amukherj)

Comment 3 Anand Avati 2014-09-05 09:45:24 UTC
COMMIT: http://review.gluster.org/8572 committed in master by Kaushal M (kaushal) 
------
commit 88159becd90d40323ecfc24cf40813538c9204cc
Author: Atin Mukherjee <amukherj>
Date:   Sat Aug 30 17:41:01 2014 +0530

    barrier: features.barrier should be a NO_DOC
    
    features.barrier is turned on/off internally by snapshot feature and hence it
    should not be exposed to the customer and this option should not be documented.
    
    Change-Id: Id9a421f94e291f1dc77044904bb18dd730c2d43e
    BUG: 1135691
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: http://review.gluster.org/8572
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>

Comment 4 Niels de Vos 2015-05-14 17:27:27 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:34 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:37:56 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:43:29 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user