Bug 1375097 - systemctl preset-all doesn't work if there is a dangling aliases present in /usr/lib/systemd/system
Summary: systemctl preset-all doesn't work if there is a dangling aliases present in /...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-12 07:46 UTC by Michal Sekletar
Modified: 2016-11-04 00:56 UTC (History)
5 users (show)

Fixed In Version: systemd-219-30.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 00:56:49 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2216 0 normal SHIPPED_LIVE systemd bug fix and enhancement update 2016-11-03 13:24:51 UTC

Description Michal 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.

Comment 1 Michal Sekletar 2016-09-12 07:50:21 UTC
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.

Comment 5 Michal Sekletar 2016-09-15 16:51:54 UTC
(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.

Comment 9 errata-xmlrpc 2016-11-04 00:56: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, 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


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