Bug 1908263

Summary: Cephfs nfs export should not be created with non-existent path
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Yogesh Mane <ymane>
Component: DocumentationAssignee: Anjana Suparna Sriram <asriram>
Documentation sub component: File System Guide QA Contact:
Status: CLOSED WORKSFORME Docs Contact:
Severity: low    
Priority: medium CC: asriram, ceph-eng-bugs, gfarnum, hyelloji, pdonnell, rmandyam, vereddy, vshankar
Version: 5.0Keywords: Reopened
Target Milestone: ---   
Target Release: 6.1z2   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2170739 (view as bug list) Environment:
Last Closed: 2023-09-15 06:13:15 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: 2170739    

Comment 1 Varsha 2020-12-31 12:32:54 UTC
Volume/nfs interface expects a valid path. I have updated the doc with this PR[https://github.com/ceph/ceph/pull/38742].

Comment 2 Hemanth Kumar 2021-04-27 04:37:34 UTC
@varsha,

Can we restrict creation of a export when the non existent path is used ?

Comment 3 Varsha 2021-04-27 06:26:01 UTC
No, see my earlier comment. We expect valid path to be specified.

Comment 5 Varsha 2021-04-29 12:59:30 UTC
We can but we will have to mount cephfs. For now I would prefer not doing it.

Comment 14 Ram Raja 2021-12-15 00:55:54 UTC
Even with master (17.x) the `ceph nfs` command to create NFS export of non-existent CephFS paths succeeds. The mgr/nfs module does not check whether the CephFS path exists. As mentioned earlier in this BZ, the mgr/nfs module would need a CephFS client to do this.

The other solution could be to rely on the NFS-Ganesha server to report back error to mgr/nfs module when reloading its exports of which one export cannot be created. For this, https://github.com/nfs-ganesha/nfs-ganesha/issues/757 would have to be solved. This would allow the mgr/nfs module to fail the `ceph nfs export create` of non-existent CephFS paths.

@Yogesh Mane, can you check if you can remove/clean up the incorrect export using the `ceph nfs export rm` command?

Comment 17 Greg Farnum 2022-01-05 23:48:37 UTC
Moving this out to 6.0 and resetting to NEW — we don't even have a viable solution to work towards at this time.

Comment 22 Venky Shankar 2022-12-09 04:25:25 UTC
Upstream tracker - https://tracker.ceph.com/issues/58228

The doc changes should already be available downstream, Yogesh - https://github.com/ceph/ceph/pull/38742

Comment 23 Yogesh Mane 2022-12-14 14:06:17 UTC
Hi Venky,

I am not seeing these changes in https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html-single/file_system_guide/index 

Could provide the link of downstream doc?

Comment 38 Red Hat Bugzilla 2024-01-14 04:25:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days