On Tue, Apr 25, 2023 at 10:56 PM Charles Rinnoch <lists.opensuse-support@difrenchal.scot> wrote:
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.
...
Provide full output of journalctl -b --full --no-pager
This is at paste.opensuse.org/pastes/840930d8954d
Well ... NetworkManager-wait-online calls "nm-online -s". According to documentation, it should wait until NetworkManager startup is complete and it sounds like "startup complete" includes activation of connections ... except it does not. Apr 25 20:37:11 smolevo NetworkManager[1079]: <info> [1682451431.7623] manager: startup complete Apr 25 20:37:11 smolevo systemd[1]: Finished Network Manager Wait Online. ... Apr 25 20:37:22 smolevo NetworkManager[1079]: <info> [1682451442.0321] dhcp4 (wlan0): address 172.20.30.40 ... Apr 25 20:37:22 smolevo NetworkManager[1079]: <info> [1682451442.0563] manager: NetworkManager state is now CONNECTED_LOCAL Apr 25 20:37:22 smolevo NetworkManager[1079]: <info> [1682451442.0572] manager: NetworkManager state is now CONNECTED_SITE ... Apr 25 20:37:22 smolevo NetworkManager[1079]: <info> [1682451442.4698] manager: NetworkManager state is now CONNECTED_GLOBAL So the interface gets an IP address ten seconds after NetworkManager startup is complete. I cannot tell whether this is a bug in NetworkManager or something is missing in configuration, but the most straightforward workaround is to wait for the online state, instead of startup. Edit NetworkManager-wait-online.service and remove "-s" from nm-online call. Replace ExecStart=/bin/bash -c "if [ ${NM_ONLINE_TIMEOUT} -gt 0 ]; then /usr/bin/nm-online -s -q --timeout=${NM_ONLINE_TIMEOUT} ; else /bin/true ; fi" with ExecStart=/bin/bash -c "if [ ${NM_ONLINE_TIMEOUT} -gt 0 ]; then /usr/bin/nm-online -q --timeout=${NM_ONLINE_TIMEOUT} ; else /bin/true ; fi"