-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.7
-
None
-
None
-
Low
-
Customer Facing, Customer Reported
-
rhel-security-selinux
-
None
-
False
-
False
-
-
No
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
A customer can see the restorecond service startup fail in timeout during boot, from time to time:
Jan 19 04:15:40 xxx systemd[1]: Starting Restorecon maintaining path file context...
[...]
Jan 19 04:17:10 xxx systemd[1]: restorecond.service: Failed with result 'timeout'.
Jan 19 04:17:10 xxx systemd[1]: Failed to start Restorecon maintaining path file context.
As per comment from [~lnykryn@redhat.com] in RHEL-138414 the implementation of restorecond is not correct.
What is the impact of this issue to you?
Failure to start restorecond automatically on boot
Please provide the package NVR for which the bug is seen:
policycoreutils-restorecond-3.6-3.el9.x86_64
How reproducible is this bug?
Quite often for customer, wasn't able to reproduce myself.
- clones
-
RHEL-138414 systemd complains with "Can't open PID file /run/restorecond.pid (yet?) after start: Operation not permitted", which is a confusing message
-
- In Progress
-