Bug 927630

Summary:	root-squash: root-squashing does not get disabled dynamically
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Bhat <rabhat>
Component:	glusterd	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED ERRATA	QA Contact:	Saurabh <saujain>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	2.0	CC:	amarts, gluster-bugs, mzywusko, rhs-bugs, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.8rhs-1	Doc Type:	Known Issue
Doc Text:	'root-squash' option on the volume, once set, won't get disabled by 'gluster volume set <VOL> root-squash disable' command. Workaround : 'stop' and 'start' the volume to disable root-squashing.	Story Points:	---
Clone Of:	927616
Clones:	964032 (view as bug list)		Environment:
Last Closed:	2013-09-23 22:39:33 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:	927616
Bug Blocks:	964032

Description Raghavendra Bhat 2013-03-26 11:38:50 UTC

+++ This bug was initially created as a clone of Bug #927616 +++

Description of problem:
enbling root-squashing happens dynamically i.e volume restart is not needed and the applications get the root-squashing effect directly. But when root-squashing is disabled volume restart is needed for actually disabling squashing (only volfile gets updated).

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Raghavendra Bhat 2013-04-05 06:31:40 UTC

https://code.engineering.redhat.com/gerrit/#/c/4542/ has been submitted for review.

Comment 3 Amar Tumballi 2013-05-17 05:23:22 UTC

Merged as part of the rebase from upstream for rhs-2.1

Comment 6 Scott Haines 2013-09-23 22:39:33 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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html

Comment 7 Scott Haines 2013-09-23 22:43:45 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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html