Bug ID | 1200290 |
---|---|
Summary | kerberized nfs mounts on a client-only config due not work due to rpc.gssd not being started |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.4 |
Hardware | x86-64 |
OS | openSUSE Leap 15.4 |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Network |
Assignee | screening-team-bugs@suse.de |
Reporter | mephisto@gmx.net |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: I installed a fresh version of OpenSUSE Leap 15.4 RC, and tried to mount kerberized nfs mounts. After configuring the mount in the yast2 nfs-client module, it fails to mount. The documentation gives the hint to execute systemctl start rpc-gssd.service after which the mount succeeds. However, this does not survive a reboot, rpc.gssd does not get startet. systemctl enable rpc-gssd.service fails. The only workaround I found was to install the nfs-server component as well, and to start the nfs kernel server with no exports. This actually brings up rpc.gssd, and mounts succeed. Please fix. Reproducible: Always Steps to Reproduce: 1. Setup kerberized NFS server 2. install fresh version of OpenSUSE Leap 15.4 3. install yast2-nfs-client + dependencies, but not nfs-kernel-server 4. configure the GSS-secured mount in yast2 nfs-client module Actual Results: mount fails with error message mount.nfs: an incorrect mount option was specified Expected Results: mount succeeds When manually starting rpc.gssd by systemctl start rpc-gssd.service, and mounting afterwards, the mount succeeds. After a reboot, rpc-gssd.service is again not running, and mount fails.