Bug 1373651

Summary:	systemd-networkd installs to multi-user.target instead of network.target.
Product:	[Fedora] Fedora	Reporter:	Ivan Viktorov <Ivan.qrt>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	24	CC:	johannbg, jsynacek, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-07 06:51:32 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:

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.