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.
DescriptionMichal Sekletar
2016-09-12 07:46:07 UTC
Description of problem:
$subject
Version-Release number of selected component (if applicable):
systemd-219-29.el7
How reproducible:
always
Steps to Reproduce:
1. Have dangling alias, e.g. /usr/lib/systemd/system/dbus-org.freedesktop.network1.service -> systemd-networkd.service
2. Execute systemctl preset-all
Actual results:
systemctl preset-all
Failed to execute operation: No such file or directory
Expected results:
systemd carries out enable/disable operations for all unit files on the system according to the current preset policy.
Additional info:
This is already fixed upstream by, https://github.com/systemd/systemd/commit/893275df36c8c358d3c0b851ca255a6169dac138. Note that we will not backport this commit as is, rather we will include only the code that is necessary to fix the bug, i.e. systemctl will *NOT* inform user about the presence of a dangling symlink.
This bug got introduced during RHEL-7.3 development. It may affect state of the system after reboot, i.e. some system services that were supposed to be running are not started. Proposing as a release blocker.
(In reply to Michal Sekletar from comment #0)
> Additional info:
> This is already fixed upstream by,
> https://github.com/systemd/systemd/commit/
> 893275df36c8c358d3c0b851ca255a6169dac138. Note that we will not backport
> this commit as is, rather we will include only the code that is necessary to
> fix the bug, i.e. systemctl will *NOT* inform user about the presence of a
> dangling symlink.
Please disregard additional info section. I did backport the change as it was upstream and user *is* informed that there is a dangling symlink present.
Example:
[0 root@qeos-141 x86_64]# systemctl preset-all
Unit dbus-org.freedesktop.network1.service is an alias to a unit that is not present, ignoring.
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, 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://rhn.redhat.com/errata/RHBA-2016-2216.html