On Wednesday, 26 April 2023 09:42:34 BST Andrei Borzenkov wrote:
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"
Thanks Andrei. That has fixed it! And thanks to everyone who has contributed. For completeness, I will document some additional info here. A useful resource is: https://doc.opensuse.org/documentation/leap/archive/42.1/reference/html/ book.opensuse.reference/cha.systemd.html That states [section 10.5.1] that systemd service files are located in /usr/ lib/systemd/system but advises to make a local copy for anything to be modified manually in /etc/systemd/system. This takes precedence for execution but is left untouched by system updates. That worked for me. This does not look like a bug in NM to me as the core functionality of NM is fine. It also looks like nm-online is behaving in accordance with its man page with the -s option doing as expected. So I am left thinking that the problem is with NetworkManager-wait-online.service. I would say your workaround, Andrei is actually the required fix, although there may be cases where the -s option is exactly what is required, in which case the solution would be a different *.service module. To fully close this out, should I log this as a bug and if so where? Regards and once again thanks CR