http://bugzilla.opensuse.org/show_bug.cgi?id=963616
http://bugzilla.opensuse.org/show_bug.cgi?id=963616#c2
sd fs
The fix doesn't seem right to me. Making nfs.service be "After=remote-fs.target" seems very odd as nfs is needed for remote-fs...
Yeah, NFS deps have my head spinning a bit. Like I said -- it 'just works' right now. If it's the best or not, or breaks something else, just don't know yet.
Requiring network-online makes a bit more sense, but it isn't really the nfs.service but rather the mounts that should require that.
Where is your name service happening? I doubt that you are running named on the VM but could you please confirm. There was a problem where named wasn't started until after remote-fs and that caused problems much like this. I think that was fixed but maybe the fix isn't in Leap yet.
I'll try to duplicate...
NS here is on the LAN, same subnet, but on different hardware. I.e., not on the DomU and not on the Dom0. Another box entirely. -- You are receiving this mail because: You are on the CC list for the bug.