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 2361672

Summary: [RFE] Request Ganesha to support binding to specific address for monitoring
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Sachin Punadikar <spunadik>
Component: CephadmAssignee: Shweta Bhosale <shbhosal>
Status: CLOSED ERRATA QA Contact: Manish Singh <manising>
Severity: medium Docs Contact: Rivka Pollack <rpollack>
Priority: unspecified    
Version: 8.0CC: akane, ben.kern, cephqe-warriors, jcaratza, kkeithle, msaini, rpollack
Target Milestone: ---Keywords: FutureFeature, RFE
Target Release: 9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-20.1.0-14 Doc Type: Enhancement
Doc Text:
.New support for NFS Ganesha binding for a specific address With this enhancement, multiple NFS Ganesha containers and daemons are now supported on a single node. NFS Ganesha binding to a specific address means that users can specify either a monitoring network, monitoring IP, or both, for monitoring purposes. The following is a specification file example: —— monitoring_ip_addrs: ceph-node-0: 192.167.100.100 ceph-node-1: 192.167.100.101 monitoring_networks: - 192.168.124.0/24 —— In addition, you can now specify the 'ip_addrs' field for service binding. —— [ceph: root@ceph-node-0 /]# cat nfs/nfs.yml service_type: nfs service_id: mynfs2 placement: hosts: - ceph-node-0 - ceph-node-1 ip_addrs: ceph-node-0: 192.168.124.100 # ceph-node-1: 192.168.124.101 networks: - 192.168.100.0/24 spec: port: 12346 monitoring_port: 678 monitoring_ip_addrs: ceph-node-0: 192.167.100.100 ceph-node-1: 192.167.100.101 monitoring_networks: - 192.168.124.0/24 ——
 Story Points: ---
Clone Of: 2359515
: 2372966 (view as bug list) Environment:
Last Closed: 2026-01-29 06:55:27 UTC Type: ---
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: 2359515    
Bug Blocks: 2372966, 2388233    

Description Sachin Punadikar 2025-04-22 14:24:31 UTC 
+++ This bug was initially created as a clone of Bug #2359515 +++

Description of problem: Request ganesha support to support a config option to specify a specific address for monitoring binding. Currently it defaults to INADDR_ANY which prevent to reuse of the same monitoring port across multiple nfs clusters https://github.com/nfs-ganesha/nfs-ganesha/blob/V6-stable/src/monitoring/exposer.cc#L200


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


How reproducible: Attempt to provision multiple ganesha clusters with the same monitoring port.


Steps to Reproduce:
1. Provision ganesha with monitoring port 9837
2. Provision another ganesha with the same monitoring port 9837
3.

Actual results:
The second ganesha cluster fails to start


Expected results:
Allow an option to specify a bind address for the monitoring service so the same port under unique addresses can bind successfully


Additional info:

--- Additional comment from Storage PM bot on 2025-04-14 14:13:28 UTC ---

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

--- Additional comment from Sachin Punadikar on 2025-04-22 10:29:20 UTC ---

Made required changes, here is PR for downstream 
https://gitlab.cee.redhat.com/ceph/nfs-ganesha/-/commit/a293a0b3f4fa5e58753bae3ae75db220fb3f20e9

Upstream code is different in file & function names. Related upstream PR - https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213832

@Thomas, please find the downstream PR in below branch 
https://gitlab.cee.redhat.com/ceph/nfs-ganesha/-/tree/private-tserlin-ceph-8.0-rhel-9-hotfix-bz2357486-patches?ref_type=heads

--- Additional comment from Sachin Punadikar on 2025-04-22 10:36:43 UTC ---

Initially there was discussion on cephadm related changes.
The main issue is how to mention the IP address for listening monitoring port.
cephadm can not pick IP address on its own. Someone need to provide the IP address for config parameter "Monitoring_Addr".
Hence cephadm changes are on hold. Need clarification from IBM Cloud team.
Comment 6 Abhishek Kane 2025-06-10 04:17:48 UTC 
Moving the RFEs out of 9.0 as they were not prioritized by PMs and engineering doesn't have bandwidth to take them up.
Comment 13 errata-xmlrpc 2026-01-29 06:55:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat Ceph Storage 9.0 Security and Enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2026:1536