1767553 – uuidd not properly configured after installation

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 1767553 - uuidd not properly configured after installation

Summary: uuidd not properly configured after installation

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	util-linux
Sub Component:
Version:	8.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	rc
Target Release:	8.0
Assignee:	Karel Zak
QA Contact:	Radka Brychtova
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-10-31 16:38 UTC by Bernd Finger
Modified:	2021-05-01 07:30 UTC (History)
CC List:	0 users
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-05-01 07:30:22 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Comment 2 Michal Hlavinka 2021-01-13 11:27:29 UTC

# rpm -qif `which uuidd`
Name        : util-linux
Version     : 2.35.2
Release     : 1.fc32
Architecture: x86_64
Install Date: Tue 09 Jun 2020 09:57:40 AM CEST
Group       : Unspecified
Size        : 14151373
License     : GPLv2 and GPLv2+ and LGPLv2+ and BSD with advertising and Public Domain
Signature   : RSA/SHA256, Wed 20 May 2020 07:14:32 PM CEST, Key ID 6c13026d12c944d0
Source RPM  : util-linux-2.35.2-1.fc32.src.rpm

^^^^^^ this shows correct compoment

Build Date  : Wed 20 May 2020 05:16:03 PM CEST
Build Host  : buildhw-04.phx2.fedoraproject.org
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : http://en.wikipedia.org/wiki/Util-linux
Bug URL     : https://bugz.fedoraproject.org/util-linux
Summary     : A collection of basic system utilities

Comment 3 Karel Zak 2021-01-14 13:23:32 UTC

I do not see a version of the uuidd package, but since version 2.32-3 we use 

%post -n uuidd
%systemd_post uuidd.service
if [ $1 -eq 1 ]; then
       /bin/systemctl start uuidd.service > /dev/null 2>&1 || :
fi

and uuidd should be started automatically after install.

Comment 4 Karel Zak 2021-01-14 13:36:08 UTC

Hmm... it seems the problem is re-install (restart), I see

Jan 14 14:25:49 ws.net.home systemd[1]: uuidd.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted.

Comment 5 Karel Zak 2021-01-14 14:45:52 UTC

OK, we need

 %preun -n uuidd
+%systemd_preun uuidd.socket
 %systemd_preun uuidd.service
 
 %postun -n uuidd
+%systemd_postun_with_restart uuidd.socket
 %systemd_postun_with_restart uuidd.service

to make it more robust.

Comment 7 RHEL Program Management 2021-05-01 07:30:22 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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