With the latest nfs-utils package, we've lost the stubs that show how to configure lockd ports. I don't really consider it a bug though, since using systemd scripts to configure it was always pretty iffy. If lockd got started up before nfs-lock.service ran you didn't get the ports set properly. Instead of reinstating those directives, how about we do something more like this patch, which encourages admins to configure them via a new /etc/modprobe.d/lockd.conf file? That should be a bit more reliable since that will make lockd listen on the correct ports no matter how it gets started up. This patch should apply directly to the rawhide dist-git in fedora.
Created attachment 913943 [details] fedora dist-git patch -- clean up and clarify lockd port configuration
nfs-utils-1.3.1-4.0.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2014-15315/nfs-utils-1.3.1-4.0.fc21
Package nfs-utils-1.3.1-4.0.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nfs-utils-1.3.1-4.0.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15315/nfs-utils-1.3.1-4.0.fc21 then log in and leave karma (feedback).
Package nfs-utils-1.3.1-4.1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nfs-utils-1.3.1-4.1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15315/nfs-utils-1.3.1-4.1.fc21 then log in and leave karma (feedback).
nfs-utils-1.3.1-4.1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.