Bug 2230484

Summary: [cephfs][config][mds] "ceph config get mds mds_symlink_recovery" fails
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: julpark
Component: CephFSAssignee: Venky Shankar <vshankar>
Status: NEW --- QA Contact: Hemanth Kumar <hyelloji>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.3CC: ceph-eng-bugs, cephqe-warriors
Target Milestone: ---   
Target Release: 7.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 julpark 2023-08-09 14:56:30 UTC
Description of problem:

"ceph config get mds mds_symlink_recovery" fails

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

16.2.10-196.el8cp

How reproducible:

ceph config get mds mds_symlink_recovery

Steps to Reproduce:
1.ceph config get mds mds_symlink_recovery
2.
3.

Actual results:

[cephuser@ceph-julpark-kcl0ip-node8 ~]$ ceph config get mds mds_symlink_recovery
Error ENOENT:

Expected results:

there should be no problem with setting the value

Additional info:

Comment 1 Venky Shankar 2023-08-10 05:33:26 UTC
(In reply to julpark from comment #0)
> Description of problem:
> 
> "ceph config get mds mds_symlink_recovery" fails
> 
> Version-Release number of selected component (if applicable):
> 
> 16.2.10-196.el8cp
> 
> How reproducible:
> 
> ceph config get mds mds_symlink_recovery
> 
> Steps to Reproduce:
> 1.ceph config get mds mds_symlink_recovery
> 2.
> 3.
> 
> Actual results:
> 
> [cephuser@ceph-julpark-kcl0ip-node8 ~]$ ceph config get mds
> mds_symlink_recovery
> Error ENOENT:

https://tracker.ceph.com/issues/46166 introduced this config as is available in RHCS6.

The fix wasn't backported to pacific - not sure why. I think we can backport this.

> 
> Expected results:
> 
> there should be no problem with setting the value
> 
> Additional info: