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.
Bug 1470525 - 'uuidd' daemon should auto-start with system but does not
Summary: 'uuidd' daemon should auto-start with system but does not
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-13 06:13 UTC by sdarade
Modified: 2021-01-27 13:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-14 08:28:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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