[Bug 809836] New: NFS mounts do not succeed at boot or resume when configured with a DNS name
https://bugzilla.novell.com/show_bug.cgi?id=809836 https://bugzilla.novell.com/show_bug.cgi?id=809836#c0 Summary: NFS mounts do not succeed at boot or resume when configured with a DNS name Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dhwprof@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 After upgrading from 12.2 to 12.3, my NFS mounts were no longer mounting automatically at boot and after suspend/resume. After some debugging, I found that the "/bin/mount -alt nfs,nfs4" command in /etc/NetworkManager/dispatcher.d/nfs was failing with the following message for each of my four NFS mounts: mount.nfs: Failed to resolve server dwserver.WalkerStreet.info: System error Typing the command into a shell, however, worked correctly. Adding "sleep 1" before the mount command in /etc/NetworkManager/dispatcher.d/nfs makes it work, as does changing the mounts to use dwserver.WalkerStreet.info's IP address, instead of the DNS name. Perhaps the DNS resolver isn't quite ready when it invokes the dispatcher script? Reproducible: Always Steps to Reproduce: 1. Configure an NFS mount, using a DNS name for the host. 2. Suspend and resume the system. 3. Actual Results: The NFS shares are no longer mounted. Expected Results: The NFS shares are mounted. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=809836 https://bugzilla.novell.com/show_bug.cgi?id=809836#c Xiaolong Li <xlli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xlli@suse.com AssignedTo|bnc-team-screening@forge.pr |puzel@suse.com |ovo.novell.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=809836 https://bugzilla.novell.com/show_bug.cgi?id=809836#c Petr Uzel <puzel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED CC| |mt@suse.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=809836 https://bugzilla.novell.com/show_bug.cgi?id=809836#c2 Christos Gourdoupis <xrigou@otenet.gr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xrigou@otenet.gr --- Comment #2 from Christos Gourdoupis <xrigou@otenet.gr> 2013-07-19 12:10:34 UTC --- The erroneous behavior may also be observed if just the network interface is brought down and up again. The suggested workaround also seems to work. -- 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.
participants (1)
-
bugzilla_noreply@novell.com