Bug 1285741

Summary: root and nodbody user file editing test case failed with a tiering volume with nfs-ganesha
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Apeksha <akhakhar>
Component: tierAssignee: Soumya Koduri <skoduri>
Status: CLOSED NOTABUG QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: asrivast, byarlaga, jthottan, kkeithle, ndevos, rhs-bugs, skoduri, storage-qa-internal, vagarwal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 05:54:17 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 Apeksha 2015-11-26 11:31:30 UTC
Description of problem:
root and nodbody user file editing test case failed with a tiering volume with nfs-ganesha

Version-Release number of selected component (if applicable):
glusterfs-3.7.5-7.el7rhgs.x86_64
nfs-ganesha-gluster-2.2.0-11.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a tired volume
2. Mount it using nfs-ganesha vers=3
3. Create a file and change its permission to 700.
4. Now edit the config file of the volume and set Root squash and run-refresh config.
5. Now try to read/write the file, it works. (But it should fail since rootsquash is enabled)

The testcase passes for a non-tiered volume, read/write is not allowed for that file

Actual results: 


Expected results:


Additional info:

Comment 4 Soumya Koduri 2015-12-01 09:53:20 UTC
As updated in https://bugzilla.redhat.com/show_bug.cgi?id=1285747#c5, I am unable to hit the issue even with tiered volume.

Comment 5 Apeksha 2015-12-02 05:54:17 UTC
Not able to reproduce it again, ran my scripts couple of times. The setup was actually in a wiered state, looks like it was a configuration issue.