Bug 1470525

Summary: 'uuidd' daemon should auto-start with system but does not
Product: Red Hat Enterprise Linux 7 Reporter: sdarade <sdarade>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: bfinger, santony
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-14 08:28:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sdarade 2017-07-13 06:13:06 UTC 
Description of problem:

uuidd daemon should auto-start with system but does not

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

uuidd-2.23.2-33.el7_3.2.x86_64


How reproducible:


Steps to Reproduce:
1.Install uuidd-2.23.2-33.el7_3.2.x86_64
2.system enable uuidd
3.system start uuidd

Actual results:

Does NOT auto-start with reboot

Expected results:

Should auto-start with reboot

Additional info:


Workaround:

Add following in /usr/lib/systemd/system/uuidd.service

[Install]
WantedBy=multi-user.target
Comment 2 Michal Hlavinka 2017-07-13 08:16:36 UTC 
uuidd comes from uuidd package (created from util-linux srpm), not uuid package. reassigning
Comment 3 Karel Zak 2017-07-14 08:21:42 UTC 
The service uses socket-activation. It does not have to run, it's started by systemd on demand (when libbuuid ask for time based UUID, e.g. "uuidgen -t"). The important is socket in this case, see:

# systemctl status uuidd.socket
● uuidd.socket - UUID daemon activation socket
   Loaded: loaded (/usr/lib/systemd/system/uuidd.socket; enabled; vendor preset: enabled)
   Active: active (listening) since Fri 2017-07-14 10:19:35 CEST; 1s ago
   Listen: /var/uuidd/request (Stream)

(this is from fedora)

If you want to be really sure that all works as expected than use "strace uuidgen -t" after reboot. You have to see that the util connects to the uuidd socket.

Not a bug from my point of view.
Comment 4 Karel Zak 2017-07-14 08:28:43 UTC 
Note that ideal solution would be to use "enable uuidd.socket" in the spec file rather than "enable uuidd.service", but it's not so important.