[Bug 248561] New: Latest autofs patch breaks NIS
https://bugzilla.novell.com/show_bug.cgi?id=248561 Summary: Latest autofs patch breaks NIS Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: aaronw@doofus.org QAContact: qa@suse.de autofs-4.1.4-62.1 seems to have broken NIS. After applying the patch I get the error automount[5145]: failed to create iautofs directory /home automount[5145]: /home: mount failed! With the previous version I have no problems. I get this for all mountpoints. Furthermore, if I create /home before starting autofs then it mounts correctly. However, as soon as I reboot, the /home directory is deleted and autofs fails again the same way. This is really annoying as our company uses NIS extensively for automount support. Your patch breaks this. The changelog says that this patch was made by mkoenig [at] suse [dot] de. Thanks. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248561 ------- Comment #1 from aaronw@doofus.org 2007-02-23 17:16 MST ------- Note that this fails for both the 32-bit and 64-bit and that autofs-4.1.4-53 works fine. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248561 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |mkoenig@novell.com |screening@forge.provo.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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248561 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from mkoenig@novell.com 2007-02-26 03:51 MST ------- This upstream patch has been applied to resolve #229607. Unfortunately it introduced this annoying issue. Do you have your filesystem in fstab declared with LABEL (or UUID)? As far as I know this issue appears only if this is the case. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248561 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE ------- Comment #3 from mkoenig@novell.com 2007-02-26 03:52 MST ------- *** This bug has been marked as a duplicate of bug 244945 *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248561 ------- Comment #4 from aaronw@doofus.org 2007-02-26 10:02 MST ------- I am running with LVM. I have 4 paritions. /dev/sda1 is a Windows NTFS partition /dev/sda2 is EXT3 (non-LVM) for /boot (1GB) labeled "Boot" /dev/sda3 is swap (non-LVM) 6GB /dev/sda4 is LVM2 On the LVM I have the root filesystem set up as XFS labeled "Root" I do not have a /home partition since that is always mounted via NIS over NFS. I think our NIS servers are Solaris and the NFS servers are a combination of Solaris and Net-apps. I use labels and not UUIDs for everything except the Windows NTFS partition. Looks the same as bug 244945. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com