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 Jira Cloud for all bug tracking management.

Bug 1927716

Summary: [RFE] Configure the IP address for Ganesha
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Francesco Pantano <fpantano>
Component: CephadmAssignee: Juan Miguel Olmo <jolmomar>
Status: CLOSED DUPLICATE QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact: Karen Norteman <knortema>
Priority: high    
Version: 5.0CC: gfidente, jolmomar, sewagner, tbarron, vereddy
Target Milestone: ---Keywords: FutureFeature, RFE
Target Release: 5.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: 2021-06-10 12:19:46 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: 1820257, 1839169    

Description Francesco Pantano 2021-02-11 11:44:22 UTC
Description of problem:

The nfs ganesha service is deployed using cephadm via the spec:

---
service_type: nfs
service_id: standalone_nfs
service_name: nfs.standalone_nfs
placement:
  hosts:
    - oc0-controller-0
    - oc0-controller-1
    - oc0-controller-2
spec:
  namespace: ganesha
  pool: manila_data

where the port and a few other parameters can be specified.
However, when the spec section described above is processed, this component is
started on  *::<port>, instead of using the cluster network or the ip address on a specific network defined by the operator.
This is a gap compared to ceph-ansible, which is able to provide this kind of feature via [1]


[1] https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-nfs/templates/ganesha.conf.j2

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Juan Miguel Olmo 2021-04-23 06:47:23 UTC
@francesco: Although we have now the "networks" attribute in service specs. We still do not have the modifications in the nfs-ganesha template. I move it again to 5.1 increasing priority

Comment 3 Sebastian Wagner 2021-06-10 12:19:46 UTC

*** This bug has been marked as a duplicate of bug 1926629 ***