Bug 1373651 - systemd-networkd installs to multi-user.target instead of network.target.
Summary: systemd-networkd installs to multi-user.target instead of network.target.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 21:30 UTC by Ivan Viktorov
Modified: 2016-09-07 06:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-07 06:51:32 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ivan Viktorov 2016-09-06 21:30:58 UTC 
Description of problem:
systemd-networkd installs to multi-user.target instead of network.target. Same for systemd-resolved.service.

Version-Release number of selected component (if applicable):
Fedora 24, systemd-229-13.fc24.

How reproducible:
Always

Steps to Reproduce:
1.systemctl enable systemd-networkd.service systemd-resolved.service
2.
3.

Actual results:
Services are installed to multi-user.target.

Expected results:
Services are installed to network.target, because they are network services.


Also, maybe its better to replace WantedBy to RequiredBy for networking services, to stop network.target and network-online.target, if some network service fails? And stop all services, that require network. Should I create a separate issue?
Comment 1 Jan Synacek 2016-09-07 06:51:32 UTC 
Neither NetworkManager nor systemd-network are installed into network.target. See man systemd.special(7).

RequiredBy is definitely not what we want, since that would mean that the networking *must* be running. I'm pretty sure that there are systems that don't need/want network to be up.
Note You need to log in before you can comment on or make changes to this bug.