RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1871934 - systemd-resolved is not its own package and is enabled by default and should not be
Summary: systemd-resolved is not its own package and is enabled by default and should ...
Keywords:
Status: CLOSED DUPLICATE of bug 1844465
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-24 15:55 UTC by Trevor Hemsley
Modified: 2020-08-25 09:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-25 09:26:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.