Bug 1286021

Summary: rootsquash cases failing inconsistently with nfs-ganesha
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Apeksha <akhakhar>
Component: nfs-ganeshaAssignee: Bug Updates Notification Mailing List <rhs-bugs>
Status: CLOSED NOTABUG QA Contact: storage-qa-internal <storage-qa-internal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: akhakhar, jthottan, kkeithle, ndevos, nlevinki, skoduri
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-08 06:15:29 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:
Attachments:
Description Flags
ganesha.log none

Description Apeksha 2015-11-27 09:11:01 UTC 
Description of problem:
rootsquash cases failing inconsistently 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:
Inconsistent

Steps to Reproduce:
1. Create  a dist-rep volume
2. Run the rootquash automated testcases with nfs-ganesha with vers=3, few cases fail
3. Same is the case when run rootsquash automated testcases with vers=4

If i teardown the setup and set it up again, and run the automated rootsquash testcases again, the cases which failed previosly now passes but few other cases fail.

Attaching the ganesha.log, packet trace(tcpdump)  and ganesha-gfapi.lof

Actual results:


Expected results:


Additional info:
Comment 2 Apeksha 2015-11-27 09:21:31 UTC 
sosreport, ganesha.log, packet trace(tcpdump)  and ganesha-gfapi.log can be found at : http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1286021/
Comment 4 Apeksha 2015-12-08 06:15:29 UTC 
Looks like, it was a setup issue, the VIP was being used by other setup also.
Ran the automated cases couple of times, dint hit this issue, closing it.