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.
DescriptionTomasz Kepczynski
2019-05-01 12:37:06 UTC
Description of problem:
After reapplying selinux-policy-targeted with:
# touch /.autorelabel
and rebooting (twice, one manual, one automatic) I am getting the following email notifcation:
/etc/cron.daily/logrotate:
error: stat of /var/log/boot.log failed: Brak dostępu
("Brak dostępu" means "permission denied" in Polish)
Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-229.el7_6.12
plymouth-0.8.9-0.31.20140113.el7
How reproducible:
Always
Additional info:
/var/log/boot.log is hardlinked to /var/spool/plymouth/boot.log and the policy specifies different file types for these two locations which obviously breaks at some point:
triss:~# restorecon -rv /var/log/
restorecon reset /var/log/boot.log context system_u:object_r:plymouthd_spool_t:s0->system_u:object_r:plymouthd_var_log_t:s0
triss:~# restorecon -rv /var/spool/plymouth/
restorecon reset /var/spool/plymouth/boot.log context system_u:object_r:plymouthd_var_log_t:s0->system_u:object_r:plymouthd_spool_t:s0
Either the file is incorrectly hardlinked (which is likely plymouthd issue) or the policy is incorrect (which is selinux-policy-targeted issue).
SELinux context is stored in an extended attribute of a file, so it cannot be different for 2 different file paths. In policy, we have different context though:
# matchpathcon /var/log/boot.log /var/spool/plymouth/boot.log
/var/log/boot.log system_u:object_r:plymouthd_var_log_t:s0
/var/spool/plymouth/boot.log system_u:object_r:plymouthd_spool_t:s0
plymouth developers, would it be possible to avoid having such a hardlink?
Comment 5Ray Strode [halfline]
2019-08-22 17:39:46 UTC
yea we dont' actually use that spool file anymore. we could just drop it.
[root@kvm-02-guest11 ~]# ls -lZ /var/log/boot.log
-rw-------. root root system_u:object_r:plymouthd_var_log_t:s0 /var/log/boot.log
The /var/log/boot.log is no longer hardlinked to /var/spool/plymouth/boot.log
Comment 21David Hernández Fernández
2020-09-23 12:35:30 UTC
Hey Ray, would you be so kind to let us know when the ERRATA is going to be released? I can see that it is being continuously delayed week by week, not sure if it is expected. I'm talking about RHBA-2020:54456-02. Thanks in advance.
Comment 22Michael Boisvert
2020-09-23 12:58:21 UTC
(In reply to David Hernández Fernández from comment #21)
> Hey Ray, would you be so kind to let us know when the ERRATA is going to be
> released? I can see that it is being continuously delayed week by week, not
> sure if it is expected. I'm talking about RHBA-2020:54456-02. Thanks in
> advance.
David, unfortunately the GA keeps getting pushed back due to RC blocking issues. As of right now the GA is set for September 29th.
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 (plymouth bug fix and enhancement update), 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-2020:4012
Description of problem: After reapplying selinux-policy-targeted with: # touch /.autorelabel and rebooting (twice, one manual, one automatic) I am getting the following email notifcation: /etc/cron.daily/logrotate: error: stat of /var/log/boot.log failed: Brak dostępu ("Brak dostępu" means "permission denied" in Polish) Version-Release number of selected component (if applicable): selinux-policy-targeted-3.13.1-229.el7_6.12 plymouth-0.8.9-0.31.20140113.el7 How reproducible: Always Additional info: /var/log/boot.log is hardlinked to /var/spool/plymouth/boot.log and the policy specifies different file types for these two locations which obviously breaks at some point: triss:~# restorecon -rv /var/log/ restorecon reset /var/log/boot.log context system_u:object_r:plymouthd_spool_t:s0->system_u:object_r:plymouthd_var_log_t:s0 triss:~# restorecon -rv /var/spool/plymouth/ restorecon reset /var/spool/plymouth/boot.log context system_u:object_r:plymouthd_var_log_t:s0->system_u:object_r:plymouthd_spool_t:s0 Either the file is incorrectly hardlinked (which is likely plymouthd issue) or the policy is incorrect (which is selinux-policy-targeted issue).