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 1844465 - [spec] dbus-org.freedesktop.resolve1.service file is listed as a configuration file in systemd package
Summary: [spec] dbus-org.freedesktop.resolve1.service file is listed as a configuratio...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: 8.0
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
: 1871934 1972489 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-05 13:34 UTC by Renaud Métrich
Modified: 2024-03-25 16:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:02:49 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4553 0 None None None 2020-11-04 02:03:00 UTC

Description Renaud Métrich 2020-06-05 13:34:27 UTC 
Description of problem:

A customer reported that after disabling systemd-resolved (which installs dbus-org.freedesktop.resolve1.service in /etc/systemd/system), the /etc/systemd/system/dbus-org.freedesktop.resolve1.service was showing as missing in "rpm -V systemd" output.

Digging further, it appears that the root cause is /etc/systemd/system/dbus-org.freedesktop.resolve1.service is installed in the build root, hence gets included in the systemd package when split-files.py collects the files in the build root.

split-files.py (see line 107 and 108):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
103     if n in known_files:
104         prefix = ' '.join(known_files[n].split()[:-1])
105         if prefix:
106             prefix += ' '
107     elif file.is_dir() and not file.is_symlink():
108         prefix = '%dir '
109     elif n.startswith('/etc'):
110         prefix = '%config(noreplace) '
111     else:
112         prefix = ''
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

I believe the file should be excluded, as a systemd preset should then enable the service upon systemd installation.

However there is a 2nd issue: apparently "systemctl preset systemd-resolved" doesn't work even though "systemd-resolved" is listed in systemd presets:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# grep systemd-resolved /usr/lib/systemd/system-preset/*
/usr/lib/systemd/system-preset/90-default.preset:disable systemd-resolved.service
/usr/lib/systemd/system-preset/90-systemd.preset:enable systemd-resolved.service
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Nothing happens when executing "systemctl preset systemd-resolved".


Version-Release number of selected component (if applicable):

systemd-239


How reproducible:

Always


Steps to Reproduce:
1. Disable systemd-resolved

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # systemctl disable systemd-resolved
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

2. Check RPM

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # rpm -V systemd
  [...]
  missing   c /etc/systemd/system/dbus-org.freedesktop.resolve1.service
  [...]
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

3. Try to enable systemd-resolved using the preset

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # systemctl preset systemd-resolved
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------


Actual results:

systemd-resolved is not enabled
Comment 1 David Tardon 2020-06-08 07:30:09 UTC 
(In reply to Renaud Métrich from comment #0)
> # grep systemd-resolved /usr/lib/systemd/system-preset/*
> /usr/lib/systemd/system-preset/90-default.preset:disable
> systemd-resolved.service
> /usr/lib/systemd/system-preset/90-systemd.preset:enable
> systemd-resolved.service
> 
> Nothing happens when executing "systemctl preset systemd-resolved".

This works as expected. From systemd.preset(5): "If multiple lines apply to a unit name, the first matching one takes precedence over all others." So the global setting in 90-default.preset (from redhat-release-server package) overrides the systemd setting in 90-systemd.preset.
Comment 2 Renaud Métrich 2020-06-08 07:39:42 UTC 
So this means that systemd-resolved should be disabled at boot, which isn't the case since "dbus-org.freedesktop.resolve1.service" is installed in /etc/systemd/system, so "partially" enabled (if a service does a DBus request, it will start).
Comment 3 David Tardon 2020-06-08 07:54:28 UTC 
(In reply to Renaud Métrich from comment #2)
> So this means that systemd-resolved should be disabled at boot, which isn't
> the case since "dbus-org.freedesktop.resolve1.service" is installed in
> /etc/systemd/system, so "partially" enabled (if a service does a DBus
> request, it will start).

Yes. That gets us back to the real bug: the symlink shouldn't be packaged.
Comment 11 David Tardon 2020-08-25 09:26:36 UTC 
*** Bug 1871934 has been marked as a duplicate of this bug. ***
Comment 15 errata-xmlrpc 2020-11-04 02:02:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: systemd security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4553
Comment 16 David Tardon 2021-06-16 11:08:36 UTC 
*** Bug 1972489 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.