|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd ordering race between NetworkManager.service/start and network.target/start | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Forgotten User b49zM5D78q <forgotten_b49zM5D78q> |
| Component: | Basesystem | Assignee: | openSUSE GNOME <os.gnome.maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | chcao |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Screenshot with the boot messages on the system console | ||
Update for reproducing: Still present in Tumbleweed 20150829 (after distribution update). In case wicked is messing up things here - the package wicked cannot be uninstalled due to dependency requirements. Raised a more detailed report than this one, marked duplicate. *** This bug has been marked as a duplicate of bug 950504 *** |
Created attachment 636718 [details] Screenshot with the boot messages on the system console After one of the recent updates in Tumbleweed, on booting with NetworkManager the network doesn't come up regularly. There is a boot message shown: systemd[1]: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start In some cases also the start of xinetd is involved, which I also use. I have to log on and issue rcnetwork restart manually for the NetworkManager to get activated. See also the attached screenshot.