Red Hat Bugzilla – Bug 1297123
User NFS mount in fstab prompts for authentication
Last modified: 2016-12-20 12:43:55 EST
Description of problem: User NFS mount setup in fstab. However when a user tries to mount it, they get prompted for authentication to start some systemd units. Version-Release number of selected component (if applicable): Fedora 23 How reproducible: Every time Steps to Reproduce: 1. /etc/fstab: 192.168.0.1:/export/hdd /mnt/hdd nfs user,noauto 1 1 2. (as user) mount /mnt/hdd Actual results: In GNOME: Authentication popup - "Authentication is required to manage system services or other units". If cancel get: Failed to start rpc-statd.service: Access denied At terminal: ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to manage system services or other units. Authenticating as: Jimmy (jimmy) Password: Expected results: mount command succeeds without any prompts.
Thank you for taking the time to report this issue. Unfortunately, I'm unable to re-produce the issue with the provided repro steps. Following your steps on a fresh Fedora 23 dnf updated today.The user mount succeeded without any prompts. If you have time and can still reproduce the issue, please read http://fedoraproject.org/wiki/BugsAndFeatureRequests and add a description along those lines to this bug report so we can diagnose the problem. Often minor configuration details are pivotal. e.g target NFS server details/config, error logs. Thank you. Fedora QA Team https://fedoraproject.org/wiki/QA
This seems to work for me as well fedora$ cat /etc/fstab f23:/home /mnt/home nfs user,noauto 1 1 fedora$ mount /mnt/home fedora$ umount /mnt/home
Just looked into this a bit more. I'm only prompted for a password if rpc-statd isn't already running, eg. if I've previous NFS mounted something. From a fresh reboot, with no other NFS mounts, I'm prompted for a password until I run sudo systemctl start rpc-statd
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.