Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Hello,
with RHEL 9 uuidd can not lock and write the status to /var/lib/libuuid/clock.txt
because /usr/lib/systemd/system/uuidd.service contains the following setting
ProtectSystem=strict
Based on the systemd docu
... If set to "strict" the entire file system hierarchy is mounted read-only
this results in a failure for
libuuid/src/gen_uuid.c :
state_fd = open(LIBUUID_CLOCK_FILE, O_RDWR|O_CREAT|O_CLOEXEC, 0660);
which can be seen in strace
openat(AT_FDCWD, "/var/lib/libuuid/clock.txt", O_RDWR|O_CREAT|O_CLOEXEC, 0660) = -1 EROFS (Read-only file system)
In addition to this behaviour, the failure is not logged and can't be seen on OS or uuidd process status.
Actually lock + uuid status info is an essential feature of uuidd and a failed access should be reported.
Reverting the config to
ProtectSystem=no
which was the default in RHEL 8.4, solves the issue.
Can you please fix the default config and add logging for failed access to /var/lib/libuuid/clock.txt
Kind regards
Michael
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
Hello, with RHEL 9 uuidd can not lock and write the status to /var/lib/libuuid/clock.txt because /usr/lib/systemd/system/uuidd.service contains the following setting ProtectSystem=strict Based on the systemd docu ... If set to "strict" the entire file system hierarchy is mounted read-only this results in a failure for libuuid/src/gen_uuid.c : state_fd = open(LIBUUID_CLOCK_FILE, O_RDWR|O_CREAT|O_CLOEXEC, 0660); which can be seen in strace openat(AT_FDCWD, "/var/lib/libuuid/clock.txt", O_RDWR|O_CREAT|O_CLOEXEC, 0660) = -1 EROFS (Read-only file system) In addition to this behaviour, the failure is not logged and can't be seen on OS or uuidd process status. Actually lock + uuid status info is an essential feature of uuidd and a failed access should be reported. Reverting the config to ProtectSystem=no which was the default in RHEL 8.4, solves the issue. Can you please fix the default config and add logging for failed access to /var/lib/libuuid/clock.txt Kind regards Michael