I have an unattended installation that used to work (and it works with 15.2) of 15.3 using autoyast that is failing during “System Configuration” “Configuring system according to autoinstall-settings” with:
“mount.nfs: Network is unreachable”
Once I select “Continue” the installation finished and the system is properly installed (nfs mounts and so), but then is no longer an “unattended” installation…
Is there any workaround to this new issue? (again, used to work with the “old” 15.3 and works with 15.2).
I have a similar issue, not with autoyast but at boot time. Nevertheless, the symptoms are identical: nfs.mount says “Network is unreachable” even though systemd said “Reached target Network is Online” a second earlier. Of course, I can ask systemctl to retry after the boot (and the NFS shares are then properly mounted), but this is cumbersome and is not a practical workaround for the rest of the family.
In general it is not a good idea to hang a question at the end of a thread that looks already as more or less dead. Particular not when, as you say, your case is “similar”. But remark that the OP uses autoyast, which do not. Better make a new thread with a title that covers YOUR problem. That will be more likeable draw the attention of people that might be able to help you with your subject.
Then about your problem. There are more people having problems with NFS mounts being to early, or being mounted at boot, but unmounted immediate. Many have solved this by using Automounting (take care, there are several cases where people call something automounting, but this is the real one). It will mount when some process needs it. And unmount after a certain time of no usage.
That can be done very easy today by using systemd-automount. You only have to add a few options to your /etc/fstab entry. I give you one:
Thanks a lot for your prompt answer! I will try this solution and come back to you if I have related questions.
Note that this issue does not happen systematically at every boot, but rather on and off randomly. Also, the same configuration worked without a glitch on Leap 15.2. So I suspect some kind of race conditions where NFS does not yet see the network connection established half a second earlier. But this is just a hunch.
That is the general idea. It happens for some and not for others. And then not always. Because the Automount postpones the mount to a later moment, it is like you doing it manually later, and thus works fine.
