RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1326440 - gssproxy systemd unit file contains bogus dependency on proc-fs-nfsd.mount
Summary: gssproxy systemd unit file contains bogus dependency on proc-fs-nfsd.mount
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gssproxy
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: Kaleem
Depends On:
TreeView+ depends on / blocked
Reported: 2016-04-12 16:49 UTC by James Ralston
Modified: 2018-04-10 11:10 UTC (History)
7 users (show)

Fixed In Version: gssproxy-0.7.0-7.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2018-04-10 11:09:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0709 0 None None None 2018-04-10 11:10:44 UTC

Description James Ralston 2016-04-12 16:49:05 UTC
Description of problem:

The gssproxy.service systemd unit file contains these dependencies:

Before=nfs-secure.service nfs-secure-server.service

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):


Comment 2 Robbie Harwood 2016-04-12 18:25:01 UTC
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.

Comment 3 Robbie Harwood 2017-05-02 18:38:29 UTC
(This has been fixed in Fedora.)

Comment 5 Sudhir Menon 2018-01-17 13:57:56 UTC
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
Before=nfs-secure.service nfs-secure-server.service

Comment 8 errata-xmlrpc 2018-04-10 11:09:51 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.


Note You need to log in before you can comment on or make changes to this bug.