Bug 1003840 - user.cifs option should have a way to be removed from the volume options
Summary: user.cifs option should have a way to be removed from the volume options
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Poornima G
QA Contact: surabhi
URL:
Whiteboard: config
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-03 10:39 UTC by surabhi
Modified: 2015-12-03 17:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 17:14:28 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description surabhi 2013-09-03 10:39:38 UTC
Description of problem:
user.cifs option : when try to enable or disable the options it works fine but there is no way to reset it.
Discussion from dev says that user options cannot have default values.

So we can have a way to remove the option from volume if it is no longer required.

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.30rhs-2.el6rhs.x86_64

How reproducible:


Steps to Reproduce:
1.Create a volume 
2. Do user.cifs enable
3. user.cifs disable
4. volume reset user.cifs 


If reset can not be done for user options then it would be good to have a way to remove it from volume if it is no longer required else it keeps coming on volume as user.cifs disabled.

Actual results:
volume reset user.cifs doesn't works.

Expected results:
either it should be reset or a way to remove it from volume if no longer required.

Additional info:

Comment 2 Vivek Agarwal 2015-12-03 17:14:28 UTC
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.


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