As per Bug #1431272, nfs-utils has started shipping a gssproxy config file for rpc-gssd. However, it does not tell gssproxy when the file is installed (SIGHUP, as mentioned in that bug), which means that existing users need to restart by hand. It's safe to SIGHUP gssproxy; it should only break anything if the config files are malformed.
Why can't nfs-utils restart gssproxy when the file is installed.
(In reply to Steve Dickson from comment #1) > Why can't nfs-utils restart gssproxy when the file is installed. If you can be sure that this won't result in gssproxy being started if it wasn't running, then that's fine.
(`systemctl gssproxy restart` will start gssproxy if it is not running.)
nfs-utils-2.1.1-5.rc2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f00354349b
nfs-utils-2.1.1-5.rc2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f00354349b
In rhbz#1440885 and rhbz#1431272 it is specifically requested that gssproxy be sent SIGHUP, not restarted. Please use `systemctl try-reload-or-restart` for this purpose.
nfs-utils-2.1.1-5.rc2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c84e5a7961
nfs-utils-2.1.1-5.rc2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
nfs-utils-2.1.1-5.rc2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.