https://bugzilla.novell.com/show_bug.cgi?id=845620
https://bugzilla.novell.com/show_bug.cgi?id=845620#c4
Martin Vidner changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mvidner@suse.com
AssignedTo|mvidner@suse.com |nfbrown@suse.com
Summary|YaST2 NFS cleint set up |[yast2-nfs-client] server
|hangs at 50% of completion. |without reverse DNS: set up
|Renders system unbootable. |hangs at 50% of completion.
| |Renders system unbootable.
--- Comment #4 from Martin Vidner 2013-11-15 17:07:49 CET ---
The log file says: rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to
hostname: Name or service not known
Indeed, I can mount my test server (NFS4) just fine, but if I add another IPv4
address to the server which is not resolvable to a hostname, gssd complains in
this way. Curiously enough, after the system has booted, systemctl start
nfs.service works fine even like this but it hangs the boot process (see
http://freedesktop.org/wiki/Software/systemd/Debugging/ for general help with
that)
Neil, I see /etc/sysconfig/nfs recently got the NFS_GSSD_AVOID_DNS option. IMHO
the user or YaST should not need to touch it since GSS was not explicitly
requested anyway.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
