Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Now in rhel8 all the previous NFS service aliases have been removed and replaced by their upstream names via Bug 1639432.
But looks like the gssproxy systemd script is still using that old service names as dependencies.
[root@rhel8 ~]# systemctl cat gssproxy | grep nfs
Before=nfs-secure.service nfs-secure-server.service
^^^^^^^^^ ^^^^^^^^^^^^^^
[root@rhel8 ~]# systemctl cat nfs-secure.service
No files found for nfs-secure.service.
[root@rhel8 ~]# systemctl cat nfs-secure-server.service
No files found for nfs-secure-server.service.
[root@rhel8 ~]# rpm -q gssproxy nfs-utils
gssproxy-0.8.0-5.el8.x86_64
nfs-utils-2.3.3-14.el8.x86_64
Version-Release number of selected component (if applicable):
gssproxy-0.8.0-5.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. as above
Actual results:
Before=nfs-secure.service nfs-secure-server.service
Expected results:
Before=rpc-gssd.service nfs-server.service(!not sure!)
Additional info:
# In rhel7
[root@rhel7 ~]# ll /usr/lib/systemd/system/nfs-secure*
lrwxrwxrwx. 1 root root 16 Apr 21 22:19 /usr/lib/systemd/system/nfs-secure.service -> rpc-gssd.service
[root@rhel7 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 7.6 Beta (Maipo)
Verified in gssproxy-0.8.0-14.el8
------------------------------------
[root.0 ~]# rpm -q gssproxy
gssproxy-0.8.0-14.el8.x86_64
[root.0 ~]# systemctl cat gssproxy
# /usr/lib/systemd/system/gssproxy.service
[Unit]
Description=GSSAPI Proxy Daemon
# GSSPROXY will not be started until syslog is
After=syslog.target
Before=rpc-gssd.service <<<<<<<<<<<<<<<<
[Service]
Environment=KRB5RCACHEDIR=/var/lib/gssproxy/rcache
ExecStart=/usr/sbin/gssproxy -D
# These two should be used with traditional UNIX forking daemons
# consult systemd.service(5) for more details
Type=forking
PIDFile=/var/run/gssproxy.pid
ExecReload=/bin/kill -HUP $MAINPID
[Install]
WantedBy=multi-user.target
[root.0 ~]#
[root.0 ~]# systemctl cat rpc-gssd.service
# /usr/lib/systemd/system/rpc-gssd.service
[Unit]
Description=RPC security service for NFS client and server
DefaultDependencies=no
Conflicts=umount.target
Requires=rpc_pipefs.target
After=rpc_pipefs.target
ConditionPathExists=/etc/krb5.keytab
PartOf=nfs-utils.service
[Service]
Type=forking
ExecStart=/usr/sbin/rpc.gssd
[root.0 ~]#
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.
https://access.redhat.com/errata/RHBA-2019:3515