Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
(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.
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).
(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.
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
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