Bug 921774
Summary: | NetworkManager-wait-online reports dependency errors when using network.service | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Elliott Forney <elliott.forney> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | danw, dcbw, hhorak |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-28 18:26:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Elliott Forney
2013-03-14 21:25:22 UTC
This isn't a NetworkManager bug. Please file bugs against ypbind and xinetd; they do not need to depend on NetworkManager-wait-online, they should only depend on network.target (which, as of rawhide/F20 will automatically depend on NetworkManager-wait-online if it is enabled). Filed bugs for xinetd and ypbind: Bug 1002294 Bug 1002295 Hm, I don't think we need to remove After=NetworkManager-wait-online.service. Since After= is only an ordering information (see systemd.unit(5)) and there is no other dependency on such service (no Requries=, Wants= or Also=), it shouldn't do any harm even if NetworkManager-wait-online.service is disabled/not installed at all. Elliot, are you sure the DEPEND error message vanishes after removing After=NetworkManager-wait-online.service from xinetd and ypbind unit files? I got it wrong before; you should replace NetworkManager-wait-online.service with network-online.target. That's the new abstracted target (in systemd >= 200), which is equivalent to NetworkManager-wait-online target when NM is active, but might make use of some other service in spins/distros that don't use NM. These warnings appear to have gone away for me with recent updates. I'm not sure that changing the After= is what actually did the trick but it is probably best to use network-online.target instead of NetworkManager-wait-online.service in any case. Thank you for your help! |