Description of problem: When NetworkManager and NetworkManager-wait-online are disabled (using the plain network service instead), missing dependencies on NetworkManager-wait-online are reported during boot. Version-Release number of selected component (if applicable): NetworkManager-0.9.9.0-44.git20131003.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Disable NetworkManager and NetworkManager-wait-online with systemctl. 2. Configure the network service. 3. Reboot Actual results: The following error is logged: # grep -B1 DEPEND /var/log/boot.log [ INFO ] Network Manager is not active. [DEPEND] Dependency failed for Network Manager Wait Online. Expected results: Since NetworkManager is disabled, there should be no related error messages during boot. Additional info: Closely related to https://bugzilla.redhat.com/show_bug.cgi?id=921774 NetworkManager-wait-online reports dependency errors when using network.service which was closed for Fedora 19 because the warnings magically disappeared. However, the bug is still present in Fedora 20. Quite likely, the culprit is the NetworkManager-provided symlink /usr/lib/systemd/system/network-online.target.wants/NetworkManager-wait-online.service which targets /usr/lib/systemd/system/NetworkManager-wait-online.service In fact, removing this symlink eliminates the "Dependency failed for Network Manager Wait Online." on boot. Note that network.service Wants network-online.target, which is ordered After NetworkManager-wait-online.service (OK). However, there should NOT be a network-online.target Wants ---> NetworkManager-wait-online.service (1) dependency, because NetworkManager-wait-online.service cannot be started given that we've disabled NetworkManager. ***** Also related is https://bugzilla.redhat.com/show_bug.cgi?id=997318 NetworkManager-wait-online.service should pull in network-online.target C1 (2013-08-28) confirms that a NetworkManager-wait-online.service Wants ---> network-online.target (2) relation -- the reverse of the above relation (1) -- should actually be present and soon be in Fedora 20. However, that is not yet the case: # systemctl show -p "Wants" NetworkManager-wait-online.service Wants=network.target system.slice which is confirmed by the .service file: # cat NetworkManager-wait-online.service [Unit] Description=Network Manager Wait Online Requisite=NetworkManager.service After=NetworkManager.service Wants=network.target # ==> Should be: Wants=network-online.target Before=network.target network-online.target [Service] Type=oneshot ExecStart=/usr/bin/nm-online -s -q --timeout=30 [Install] WantedBy=multi-user.target %----- Is the fix for NetworkManager-wait-online.service perhaps stuck somewhere upstream? Thanks!
There was a discussion about NetworkManager-wait-online.service in bug 1076053. Unfortunately, it was not finished and decided whether the unit is right at that time. So lets ask systemd guys once more how the unit should look like.
I don't think that there is a clean solution. I would suggest to leave things as is in released fedoras. And that drop the symlink and set WantedByt to network-online target, maybe also have the Also to this unitfile in NetworkManager service.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 think this was resolved by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d61eaf2545c819cab17c29c4c13a3a3bd94b38a6 and bug 1455704
This is of course still present in CentOS / RHEL 7 current, and will not 'bubble' in by itself. leaving a breadcrumb for those researching
I just got hit with this on the latest Debian testing. Crazy! Don't think they have fixed the same issue yet.