Bug 2363597
| Summary: | [NFS-Ganesha] Incorrect IP shown in NFS Ganesha info when bound to non-primary interface on multi-NIC server | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Manisha Saini <msaini> | |
| Component: | Cephadm | Assignee: | Shweta Bhosale <shbhosal> | |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.1 | CC: | akane, cephqe-warriors, jcaratza | |
| Target Milestone: | --- | |||
| Target Release: | 9.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ceph-20.1.0-13 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2370189 (view as bug list) | Environment: | ||
| Last Closed: | 2026-01-29 06:55:49 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: | 2370189 | |||
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 |
Description of problem: ====================== When NFS-Ganesha is deployed on a server with multiple network interfaces (multi-NIC setup), and configured to bind to a non-primary IP (e.g, via Bind_Addr or virtual_ip), the server info reported (e.g. ceph nfs cluster info) still displays the primary interface IP instead of the configured IP. This leads to misleading diagnostic output and confusion in environments where IP-based routing or isolation is used. Yaml file ---- # cat /var/lib/ceph/nfs.yaml service_type: nfs service_id: nfsganesha2 placement: hosts: - cali013 spec: port: 2050 virtual_ip: 10.8.130.96 [ceph: root@cali013 /]# ceph orch ls | grep nfsganesha2 nfs.nfsganesha2 ?:2050 1/1 6m ago 28m cali013 [ceph: root@cali013 /]# ceph nfs cluster info nfsganesha { "nfsganesha": { "backend": [ { "hostname": "cali013", "ip": "10.8.130.13", "port": 2049 } ], "virtual_ip": null } } [ceph: root@cali013 /]# It correctly adds the VIP in the "Bind_addr " of nfs ganesha configuration file. [root@cali013 ganesha]# cat ganesha.conf # This file is generated by cephadm. NFS_CORE_PARAM { Enable_NLM = false; Enable_RQUOTA = false; Protocols = 4; mount_path_pseudo = true; Enable_UDP = false; NFS_Port = 2050; allow_set_io_flusher_fail = true; Bind_addr = 10.8.130.96; Monitoring_Port = 9588; } On client ----- Mount is denied using the primary IP, which is expected # mount -t nfs -o port=2050 10.8.130.13:/ganeshavol2 /mnt/ganesha1. --> It is stuck/failed Mount is allowed with virtual IP --> [root@ceph-stretched-cluster-nfs-et0g5e-node4 mnt]# mount -t nfs -o port=2050 10.8.130.96:/ganeshavol2 /mnt/ganesha1 [root@ceph-stretched-cluster-nfs-et0g5e-node4 mnt]# df -hT | grep /mnt/ganesha1 10.8.130.96:/ganeshavol2 nfs4 27T 3.0G 27T 1% /mnt/ganesha1 Version-Release number of selected component (if applicable): ============ [ceph: root@cali013 /]# ceph --version ceph version 19.2.1-167.el9cp (3e3ca3a16912abfd58b473e2ae724703f9a0415d) squid (stable) [ceph: root@cali013 /]# rpm -qa | grep nfs libnfsidmap-2.5.4-27.el9.x86_64 nfs-utils-2.5.4-27.el9.x86_64 nfs-ganesha-selinux-6.5-12.el9cp.noarch nfs-ganesha-6.5-12.el9cp.x86_64 nfs-ganesha-ceph-6.5-12.el9cp.x86_64 nfs-ganesha-rados-grace-6.5-12.el9cp.x86_64 nfs-ganesha-rados-urls-6.5-12.el9cp.x86_64 nfs-ganesha-rgw-6.5-12.el9cp.x86_64 How reproducible: =========== Everytime Steps to Reproduce: ============ 1. Deploy a host with multiple interfaces/IPs 2. Configure Ganesha with a virtual_ip or bind it to a secondary IP (e.g. 10.8.130.96). 3. Deploy the NFS service using ceph orch apply -i nfs.yaml. 4. Check ceph nfs cluster info for the IP that used be used for mounting. Actual results: ======== NFS-Ganesha reports the system's primary IP even though it is bound to 10.8.130.96 Expected results: ========= NFS-Ganesha should show the IP it is actually bound to (e.g.10.8.130.96). Additional info: