Red Hat Bugzilla – Bug 1011853
/etc/sysconfig/nfs sets variables that are not used by the nfs service
Last modified: 2016-02-10 15:54:17 EST
Description of problem:
conf/nfs.sysconfig.in, which is used to update /etc/sysconfig/nfs,
sets variables that are no longer used in recent fedora nfs-utils
In particular, configuring iptables/firewalld to open nfs access
to the host to serve the ISO domain, does not work, as e.g. mountd
runs with its default port number and not the open opened in iptables.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run engine-setup, choose to configure an ISO domain
2. run 'ps -ef | grep mountd'
rpc.mountd runs with default options
rpc.mountd should run with '-p 892'
are they needed by .el6 still?
flagging storage for their input to this, even if implementation is covered by integration
(In reply to Itamar Heim from comment #1)
> are they needed by .el6 still?
They are not "needed". In el6, there are e.g. both MOUNTD_PORT and RPCMOUNTDOPTS. In (recent enough) fedora there is only RPCMOUNTDOPTS. So using RPCMOUNTDOPTS works on both.
Why did the people packaging nfs-utils on fedora "went back"? I guess because they wanted to run the various daemons from systemd directly, without going through wrapper scripts. Doing something like
[ -n "$MOUNTD_PORT" ] \
&& RPCMOUNTDOPTS="$RPCMOUNTDOPTS -p $MOUNTD_PORT"
in /etc/init.d/nfs on el6 is easy, but if you want something similar in systemd, you can't staff it into the service file, which is currently:
you have to make a wrapper script.
That's just a guess, of course, and while I might not agree with the decision to do that, I can understand the reasoning behind it.
Itamar, I'm not sure what the question here is?
Didi covered the technical side. I've commented on the patch.
Included in 3.3.1 beta
oVirt 3.3.1 has been released