On Monday, 24 April 2023 12:16:27 BST Andrei Borzenkov wrote:
On Mon, Apr 24, 2023 at 2:05 PM Charles Rinnoch
<lists.opensuse-support@difrenchal.scot> wrote:
Problems come when I try to use Network Manager for the setup at home, in that Network Manager is not invoked [by systemd?] at the same point as Wicked is. It is.
Wicked is synchronous, its unit completes startup after interfaces have been configured. NetworkManager is asynchronous - when NetworkManager unit completed startup, it just means the daemon was started. Daemon proceeds to establish connections concurrently with any other startup activity.
You need to enable NetworkManager-wait-online.service which will delay followup processing until NteworkManager reports it reached online state. NFS mount points automatically order themselves after network-online.target (which will be after NetworkManager-wait-online.service). If you have some custom units that need network on startup, you need to order them after network-online.target manually.
Thanks Andrei, but no joy. systemctl status NetworkManager-wait-online.service tells me that this service runs for 4s or so, but systemctl status tells me that the overall status is 'degraded'. systemctl --failed tells me that the unit import-home.mount failed. However, if I run systemctl start import-home.mount then the mount is made successfully - ie I get the sytem running as I want it. This tells me that Network Manager is fundamentally working and I think I have a race condition with the mount being called too soon. I have taken a look at /run/systemd/generator/import-home.mount under both Wicked and NM and they are the same and appear to be regenerated when I use YaST to switch between NM and Wicked. So a race which works out OK under Wicked but not NM? Or something else about NM not being set up right? Overall, as I have said elsewhere, so far I have learned that both NM and Wicked can provide any of my use cases - the differences between the 2 [as far as the user is concerned] relate to the availability and utility of the tools [YaST, nmtui etc] to set them up and how they are set up within systemd. Anyway, appreciative of the help so far and would welcome any more help. Systems are Leap 15.4. Issue manifests on Wireless for laptop and Ethernet for Desktop although conducting investigations on laptop only at the moment. Also my network runs a fixed IP plus a DHCP on network interfaces, although the problem still manifests with fixed IP only on the same subnet as the nfs server. Regards CR