Bug 1286900 - FSAL_GLUSTER : Rename throws error in mount when acl is enabled
Summary: FSAL_GLUSTER : Rename throws error in mount when acl is enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: nfs-ganesha
Classification: Retired
Component: FSAL_GLUSTER
Version: devel
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Jiffin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1289483
TreeView+ depends on / blocked
 
Reported: 2015-12-01 04:51 UTC by Jiffin
Modified: 2020-06-24 11:17 UTC (History)
2 users (show)

Fixed In Version: nfs-ganesha-2.4-dev-3
Clone Of:
: 1289483 (view as bug list)
Environment:
Last Closed: 2020-06-24 11:17:08 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.