Bug 763769 (GLUSTER-2037)

Summary:	3.1.1-QA4: CIFS access is not being configured correctly
Product:	[Retired] GlusterSP	Reporter:	Jacob Shucart <jacob>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	3.1.0	CC:	platform, shireesh
Target Milestone:	3.1.2
Target Release:	---
Hardware:	All
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jacob Shucart 2010-10-28 17:58:08 UTC

If I create some users and then add CIFS access restricted to those users, I am still able to connect to the CIFS share with read-only access and I can copy files out of the share.  Write access is restricted as it should be, but both of them should be disabled if we are restricting access.

Comment 1 Balamurugan Arumugam 2010-10-29 05:56:12 UTC

We are not able to reproduce this behavior.

However expected behavior is as follows,

After changing allowed users of a volume through management console, opened volume in MS Windows are still fully accessible unless user logs off from the system.  The session is not closed by Samba.

Admin needs to force restart the volume to destroy opened sessions.

Comment 2 Jacob Shucart 2010-10-29 11:53:35 UTC

This was a new volume and the first time I connected to it from my Windows 7 64-bit laptop.