Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2224169

Summary: ceph nfs cluster create does not support 'label' tag via CLI
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Anjali <amenon>
Component: CephadmAssignee: Adam King <adking>
Status: CLOSED DEFERRED QA Contact: Mohit Bisht <mobisht>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.3CC: adking, ceph-eng-bugs, cephqe-warriors, csharpe, gfarnum, nia, nthomas, sostapov
Target Milestone: ---   
Target Release: 6.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-08-28 10:41:21 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:

Description Anjali 2023-07-20 05:24:35 UTC 
Description of problem:

- IHAC who can create a service for ingress that supports labels from the ceph dashboard however from CLI you cannot specify the label in the placement.

- For example this doesn't error but it doesn't setup the service with a placement label.
 
# ceph nfs cluster create nfscluster3 "2 label:mds" --ingress 10.37.32.10

- Need help from engineering whether it is possible to pass 'label' tag via CLI. 

[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html-single/file_system_guide/index#exporting-ceph-file-system-namespaces-over-the-nfs-protocol_fs

[2] https://docs.ceph.com/en/pacific/mgr/nfs/#create-nfs-ganesha-cluster

Version-Release number of selected component (if applicable):
- ceph version 16.2.10-138.el8cp

Steps to Reproduce:
[root@ceph5-mons1 ~]# ceph fs volume create testnfs --placement="2 ceph5-osds3 ceph5-osds2"

[root@ceph5-mons1 ~]# ceph fs ls
name: testfs, metadata pool: cephfs.testfs.meta, data pools: [cephfs.testfs.data ]
name: testnfs, metadata pool: cephfs.testnfs.meta, data pools: [cephfs.testnfs.data ]

[root@ceph5-mons1 ~]# ceph nfs cluster create testnfs "2 label:mds" --ingress 10.68.64.10

Actual results:

- Unable to setup the service with a placement label

Expected results:

- able to setup the service with a placement label
Comment 1 Scott Ostapovicz 2023-07-20 14:07:42 UTC 
Too late to assign new issues to the 6.1 z1 target.  Retargeting to 6.1 z2.
Comment 2 Kaleb KEITHLEY 2023-07-20 18:49:19 UTC 
Is this dashboard, or something else?
Comment 3 csharpe 2023-07-26 03:09:48 UTC 
Cu is saying the issue is with the cli as you cannot specify the label in the placement from the cli.

For example this doesn't error but it doesn't setup the service with a placement label.
 
# ceph nfs cluster create nfscluster3 "2 label:mds" --ingress 10.37.32.10

Cu confirmed this is possible from the dashboard, hence, they believe this is a bug with the cli.
Comment 4 Kaleb KEITHLEY 2023-07-26 12:03:05 UTC 
(In reply to csharpe from comment #3)
> Cu is saying the issue is with the cli as you cannot specify the label in
> the placement from the cli.
> 
> For example this doesn't error but it doesn't setup the service with a
> placement label.
>  
> # ceph nfs cluster create nfscluster3 "2 label:mds" --ingress 10.37.32.10
    ^^^^

> 
> Cu confirmed this is possible from the dashboard, hence, they believe this
> is a bug with the cli.

This is either the dashboard or the cli — nothing to do with ganesha functionality.
Comment 7 Nizamudeen 2023-08-09 10:18:31 UTC 
I moving it to cephFS. please change the component if this is wrong!
Comment 14 Sahina Bose 2025-08-28 10:41:21 UTC 
Closing this bug as part of bulk closing of bugs that have been open for more than 2 years without any significant updates for the last 3 months. Please reopen with justification if you think this bug is still relevant and needs to be addressed in an upcoming release
Comment 15 Red Hat Bugzilla 2025-12-27 04:25:08 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days