Bug 2359515 - Request Ganesha to support binding to specific address for monitoring [NEEDINFO]
Summary: Request Ganesha to support binding to specific address for monitoring
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: NFS-Ganesha
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 8.1
Assignee: Sachin Punadikar
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 2361672 2372966
TreeView+ depends on / blocked
 
Reported: 2025-04-14 14:13 UTC by ben.kern
Modified: 2025-06-26 12:24 UTC (History)
5 users (show)

Fixed In Version: nfs-ganesha-6.5-11.el9cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2361672 (view as bug list)
Environment:
Last Closed: 2025-06-26 12:24:04 UTC
Embargoed:
spunadik: needinfo? (ben.kern)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-11163 0 None None None 2025-04-14 14:17:01 UTC
Red Hat Issue Tracker RHCEPH-11164 0 None None None 2025-04-14 14:17:05 UTC
Red Hat Product Errata RHSA-2025:9775 0 None None None 2025-06-26 12:24:16 UTC

Description ben.kern 2025-04-14 14:13:18 UTC
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:

Comment 1 Storage PM bot 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.

Comment 2 Sachin Punadikar 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

Comment 3 Sachin Punadikar 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 4 Sachin Punadikar 2025-04-23 05:45:44 UTC
Need to add "Monitoring_Addr" entry in ganesha.conf file with the IP address on which Monitoring module will listen.

NFS_CORE_PARAM {
        mount_path_pseudo = true;
        Protocols = 4;
        Enable_UDP = false;
        Enable_RQUOTA = false;
        NFS_Port = 2049;
        Monitoring_Addr = 10.8.152.13;    <= Entry indicating monitoring address
}

If "Monitoring_Addr" is not added to ganesha.conf file, then its default action is to listen on all IP addresses.

Comment 13 errata-xmlrpc 2025-06-26 12:24:04 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 (Important: Red Hat Ceph Storage 8.1 security, bug fix, and enhancement updates), 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-2025:9775


Note You need to log in before you can comment on or make changes to this bug.