Bug 1167613

Summary: BVT: Setting "user.cifs" to disable is not removing the Samba share from smb.conf
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Lalatendu Mohanty <lmohanty>
Component: sambaAssignee: Raghavendra Talur <rtalur>
Status: CLOSED ERRATA QA Contact: Lalatendu Mohanty <lmohanty>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.0CC: asrivast, nlevinki, rcyriac, sbhaloth, vagarwal
Target Milestone: ---Keywords: Regression, ZStream
Target Release: RHGS 3.0.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.6.0.35-1.el6rhs Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-15 13:42:55 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:    
Bug Blocks: 1162694    

Description Lalatendu Mohanty 2014-11-25 07:32:50 UTC
Description of problem:

Setting "user.cifs" to disable for a volume used to remove the configuration settings for the volume from smb.conf, so that the Samba share is not available any-more. However it is not working  in latest RPMs.  

Version-Release number of selected component (if applicable):

glusterfs-3.6.0.33-1.el6rhs.x86_64 and glusterfs-3.6.0.34-1.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. create a volume and start it
2. check "testparm -s" output. it should have the volume config
3. gluster volume set <volume> user.cifs disable
4. check "testparm -s" output. it should not have the volume config

Actual results:

Volume info present in smb.conf

Expected results:

After running "volume set <volume> user.cifs disable" smb.conf should not have the volume info.

Additional info:

[root@rhsauto056 ~]# gluster volume set testvol user.cifs disable
volume set: success

[root@rhsauto056 ~]# gluster v info
 
Volume Name: testvol
Type: Distribute
Volume ID: 01be3bf8-da56-4a41-99f3-102996438870
Status: Started
Snap Volume: no
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 10.70.40.131:/bricks/testvol-b1
Brick2: 10.70.40.131:/bricks/testvol-b2
Options Reconfigured:
user.cifs: disable
performance.readdir-ahead: on
snap-max-hard-limit: 256
snap-max-soft-limit: 90
auto-delete: disable


#testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Can't find include file /etc/samba/ctdb.conf
Processing section "[gluster-testvol]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
[global]
	workgroup = MYGROUP
	server string = Samba Server Version %v
	log file = /var/log/samba/log.%m
	max log size = 50
	max protocol = SMB2
	ctdbd socket = /tmp/ctdb.socket
	load printers = No
	disable spoolss = Yes
	show add printer wizard = No
	stat cache = No
	kernel oplocks = No
	idmap config * : backend = tdb
	printing = bsd
	cups options = raw
	print command = lpr -r -P'%p' %s
	lpq command = lpq -P'%p'
	lprm command = lprm -P'%p' %j
	map archive = No
	map readonly = no
	store dos attributes = Yes

[gluster-testvol]
	comment = For samba share of volume testvol
	path = /
	read only = No
	guest ok = Yes
	vfs objects = glusterfs
	glusterfs:loglevel = 7
	glusterfs:logfile = /var/log/samba/glusterfs-testvol.%M.log
	glusterfs:volume = testvol

Comment 1 Raghavendra Talur 2014-12-01 13:15:18 UTC
https://code.engineering.redhat.com/gerrit/#/c/37464/ fixes this.

Comment 2 Lalatendu Mohanty 2014-12-10 11:31:33 UTC
The issue is fixed in recent BVT runs i.e. build glusterfs-3.6.0.37-1.el6rhs.x86_64 , hence marking this as verified

Comment 4 errata-xmlrpc 2015-01-15 13:42:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0038.html