Bug 2047952

Summary: rpm -V / --verify reports bad user/group/mtime for /run/uuidd
Product: Red Hat Enterprise Linux 9 Reporter: Jiri Jaburek <jjaburek>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: Vojtech Eichler <veichler>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: veichler
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: util-linux-2.37.3-2.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2059241 (view as bug list) Environment:
Last Closed: 2022-05-17 16:04:52 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:
Bug Depends On:    
Bug Blocks: 2059241    

Description Jiri Jaburek 2022-01-28 23:02:10 UTC
Description of problem:

When initially installing uuidd, the file has correct permissions and rpm -V is empty:

# rpm -V uuidd
# ls -ld /run/uuidd
drwxrwsr-x. 2 uuidd uuidd 60 Jan 28 23:51 /run/uuidd

This matches the packaged

  %dir %attr(2775, uuidd, uuidd) /run/uuidd

However after a reboot, rpm -V reports an error:

# rpm -V uuidd
.M...UG..    /run/uuidd
# ls -ld /run/uuidd
drwxr-xr-x. 2 root root 60 Jan 28 23:52 /run/uuidd

This is probably because there's no tmpfiles.d entry to pre-create /run/uuidd with the right user/group and mode bits. Consider either adding one, or resolving this another way. Thanks!


Version-Release number of selected component (if applicable):
uuidd-2.37.2-1.el9

Comment 1 Karel Zak 2022-02-02 11:06:00 UTC
Good catch.

Comment 8 errata-xmlrpc 2022-05-17 16:04:52 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 (new packages: util-linux), 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://access.redhat.com/errata/RHBA-2022:4082