Description of problem: systemd-udev-settle.service Version-Release number of selected component (if applicable): device-mapper-multipath-0.8.2-1.fc32.x86_64 How reproducible: Always, every boot Steps to Reproduce: 1. Clean install Fedora Workstation 32/Rawhide, and reboot 2. 3. Actual results: Drags in systemd-udev-settle.service, increases boot time by 1-3 seconds. Expected results: a. I expect this systemd unit should be disabled by default, but "vendor preset: enabled" b. At the least it should avoid using deprecated services that increase boot times for no good reason Additional info: $ systemctl list-dependencies multipathd.service [sudo] password for hack: multipathd.service ● ├─system.slice ● ├─systemd-udev-settle.service ● └─systemd-udev-trigger.service $ systemctl status multipathd.service ● multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● multipathd.socket Condition: start condition failed at Sun 2020-01-26 04:52:48 MST; 6min ago └─ ConditionPathExists=/etc/multipath.conf was not met Jan 26 04:52:48 localhost.localdomain systemd[1]: Condition check resulted in Device-Mapper Multipath Device Controller being skipped.
/usr/lib/systemd/system/multipathd.service contains ConditionPathExists=/etc/multipath.conf $ sudo systemctl status multipathd.service [sudo] password for chris: ● multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● multipathd.socket Condition: start condition failed at Fri 2020-01-31 09:19:26 MST; 3min 30s ago └─ ConditionPathExists=/etc/multipath.conf was not met Jan 31 09:19:26 fmac.local systemd[1]: Condition check resulted in Device-Mapper Multipath Device Controller being skipped. $ journalctl -b | grep multipath Jan 31 09:19:25 fmac.local systemd[1]: Listening on multipathd control socket. $ journalctl -b | grep settle Jan 31 09:19:26 fmac.local udevadm[610]: systemd-udev-settle.service is deprecated. Jan 31 09:19:26 fmac.local audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-udev-settle comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' $ systemd-analyze blame includes 1.545s systemd-udev-settle.service So if the condition isn't being met, why is settle dragged in? Is it merely because the socket is activated?
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
The same complaint shows up also on every Fedora 33 boot
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.