Comment # 1 on bug 963616 from Neil Brown

Thanks for the report.

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...

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...