Description of problem:
The gssproxy.service systemd unit file contains these dependencies:
The "Requires" dependency on proc-fs-nfsd.mount is completely bogus. Yes, if NFS is in use, proc-fs-nfsd.mount should be started before gssproxy.service. But in no sense does gssproxy depend on NFS. For example, we use gssproxy on our RHEL7 hosts to broker access to the Kerberos keytab file via mod_auth_gssapi.so, as described here:
The correct dependencies list should be:
Before=nfs-secure.service nfs-secure-server.service proc-fs-nfsd.mount
Version-Release number of selected component (if applicable):
Note - we are waiting for changes to NFS spec files to remove these lines. The correct way to handle this possible dependency is to have the relevant NFS services require gssproxy to be available.
(This has been fixed in Fedora.)
Verified using gssproxy-0.7.0-17.el7.x86_64 on
[root@master sssd]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 Beta (Maipo)
[root@master sssd]# cat /usr/lib/systemd/system/gssproxy.service
Description=GSSAPI Proxy Daemon
# GSSPROXY will not be started until syslog is
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.