Description of problem: Network Manager Wait Online Ignoring --timeout Parameter. Waited only 25 seconds when parameter required 60 seconds. Version-Release number of selected component (if applicable): Name : NetworkManager Epoch : 1 Version : 1.8.2 Release : 1.fc26 Arch : x86_64 How reproducible: Network doesn't take same amount of time to come online each time. Steps to Reproduce: 1. Start machine Actual results: Timed out after only 25 seconds. Expected results: Network Manager waits for the full 60 second timeout as specified in it's parameter. Additional info: ● NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-08-17 11:41:23 AEST; 9h ago Docs: man:nm-online(1) Process: 901 ExecStart=/usr/bin/nm-online -s -q --timeout=60 (code=exited, status=2) Main PID: 901 (code=exited, status=2) Aug 17 11:40:58 localhost.localdomain systemd[1]: Starting Network Manager Wait Online... Aug 17 11:41:23 localhost.localdomain nm-online[901]: Error: Could not create NMClient object: Timeout was reached Aug 17 11:41:23 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Aug 17 11:41:23 localhost.localdomain systemd[1]: Failed to start Network Manager Wait Online. Aug 17 11:41:23 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Unit entered failed state. Aug 17 11:41:23 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.
Aug 17 11:41:23 localhost.localdomain nm-online[901]: Error: Could not create NMClient object: Timeout was reached so NetworkManager service is not running? Maybe nm-online should wait longer in this case, but it doesn't seem critical, because you are supposed to start NetworkManager.service and NetworkManager-wait-online.service together.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I get exactly the same error with Fedora 30 and NetworkManager 1.16.4. ● NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-10-06 22:08:01 CEST; 7min ago Docs: man:nm-online(1) Process: 838 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited, status=2) Main PID: 838 (code=exited, status=2) oct. 06 22:07:36 localhost.localdomain systemd[1]: Starting Network Manager Wait Online... oct. 06 22:08:01 localhost.localdomain nm-online[838]: Error: Could not create NMClient object: Timeout was reached oct. 06 22:08:01 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=2/INVALIDARGUMENT oct. 06 22:08:01 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'. oct. 06 22:08:01 localhost.localdomain systemd[1]: Failed to start Network Manager Wait Online. Like in the first comment of this issue, changing to "--timeout" to a longer value change nothing, it still exit with status 2 "INVALIDARGUMENT" after 25s. If I restart the "NetworkManager-wait-online.service" after boot, it work successfully. The Network manager seem to start slowly than expected, and make this NetworkManager-wait-online bug to appear. This issue appeared the first time the october 04 2019 (Before, I didn't get network issues): -- Reboot -- sept. 28 20:04:48 localhost.localdomain systemd[1]: Starting Network Manager Wait Online... sept. 28 20:04:57 MARVIN systemd[1]: Started Network Manager Wait Online. sept. 29 00:01:03 MARVIN systemd[1]: NetworkManager-wait-online.service: Succeeded. sept. 29 00:01:03 MARVIN systemd[1]: Stopped Network Manager Wait Online. -- Reboot -- oct. 04 20:17:47 localhost.localdomain systemd[1]: Starting Network Manager Wait Online... oct. 04 20:18:13 localhost.localdomain nm-online[837]: Error: Could not create NMClient object: Timeout was reached oct. 04 20:18:13 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=2/INVALIDARGUMENT oct. 04 20:18:13 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'. oct. 04 20:18:13 localhost.localdomain systemd[1]: Failed to start Network Manager Wait Online. My current workaround is to use "/usr/bin/sleep 60" instead of the "/usr/bin/nm-online -s -q --timeout=30" command in the service unit file.