Bug 1871934

Summary:	systemd-resolved is not its own package and is enabled by default and should not be
Product:	Red Hat Enterprise Linux 8	Reporter:	Trevor Hemsley <trevor.hemsley>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	dtardon, systemd-maint-list
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
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:	2020-08-25 09:26:36 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 Trevor Hemsley 2020-08-24 15:55:16 UTC

Description of problem:
The systemd package ships the systemd-resolved unit file and enables it out of the box. This should be in its own package so that systems administrators can choose whether or not it is installed. It should also be disabled out of the box so that it doesn't run automatically - particularly important if you're going to ship it under the radar like this.

Version-Release number of selected component (if applicable):
systemd-239-31.el8_2.2.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install systemd
2. systemctl status systemd-resolved
3.

Actual results:
It's enabled and running but if you don't configure it then  it does nothing.

Expected results:
It should not be running by default. It shouldn't even be installed by default.

Additional info:

Comment 1 David Tardon 2020-08-25 09:26:36 UTC


*** This bug has been marked as a duplicate of bug 1844465 ***