Bug 1286900

Summary:	FSAL_GLUSTER : Rename throws error in mount when acl is enabled
Product:	[Retired] nfs-ganesha	Reporter:	Jiffin <jthottan>
Component:	FSAL_GLUSTER	Assignee:	Jiffin <jthottan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	devel	CC:	kkeithle, pasik
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	nfs-ganesha-2.4-dev-3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1289483 (view as bug list)		Environment:
Last Closed:	2020-06-24 11:17:08 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:	1289483

Description Jiffin 2015-12-01 04:51:55 UTC

Description of problem:
When acl is enabled and if rename is performed gettattr() call in FSAL_GLUSTER may return ENOENT for replaced(or removed) file. This will throw an error in mount even though rename was successful.

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

How reproducible:
using pynfs test it is 100% reproducible.

Steps to Reproduce:
1.Create a volume and export it via nfs-ganesha with acl enabled
2.Run RNM15 test in the pynfs suite for nfsv4


Actual results:
throws error in mount saying "No such file or directory"

Expected results:
Should throw this error

Additional info:
Error is sent from glfs_h_acl_get() in FSAL

Comment 1 Jiffin 2015-12-01 04:53:00 UTC

Upstream patch reference https://review.gerrithub.io/#/c/253518/

Comment 2 Jiffin 2016-05-25 12:55:06 UTC

This fix cause a regression for symlinks when acl enabled.Hence the changing into assigned state

Comment 3 Kaleb KEITHLEY 2020-06-24 11:17:08 UTC

If this is still an issue please open an issue in the github tracker at https://github.com/nfs-ganesha/nfs-ganesha/issues