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 1505448

Summary: nfs-ganesha: Bind_Addr parameter ignored
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ram Raja <rraja>
Component: CephFSAssignee: Daniel Gryniewicz <dang>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 3.0CC: anharris, ceph-eng-bugs, ceph-qe-bugs, flucifre, hnallurv, john.spray, kdreyer, mbenjamin, pdonnell
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: nfs-ganesha-2.5.2-13.el7cp Ubuntu: nfs-ganesha_2.5.2-13redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:49:04 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 Ram Raja 2017-10-23 15:12:20 UTC
Description of problem:
For Manila/CephFS/Ganesha deployment in OSP 13, we need to restrict Ganesha to listen in only on specific IP addresses. The config option to do so currently doesn't work.

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


How reproducible:

Always
Steps to Reproduce:
1. Add the following block to ganesha.conf and start ganesha
#
NFS_Core_Param
{
Bind_Addr=<ip addr to bind to> ;
}
#
2. Run `netsat -ntlp` command as root to check ganesha's listening address.

Actual results:
Ganesha listens on all IP addresses.

Expected results:
Ganesha listens only on the IP address it's configured to listen on.

Additional info:

Comment 7 Daniel Gryniewicz 2017-10-24 17:16:06 UTC
A fix has been submitted upstream here:

https://review.gerrithub.io/383626

Once this is in, it can be backported.

Comment 19 errata-xmlrpc 2017-12-05 23:49: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, 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/RHBA-2017:3387