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.

Description of problem:
Updating daily RHEL8, not changing the cron configuration and around 2-4 weeks ago my crond stopped loading the /etc/crontab and complains about selinux permissions.

Version-Release number of selected component (if applicable):
crontabs-1.11-16.20150630git.el8.noarch
systemd-239-13.el8_0.3.aarch64

How reproducible:
Always

Steps to Reproduce:
1. systemctl status crond

Actual results:
Apr 25 08:34:14 gigabyte-r120-15.khw3.lab.eng.bos.redhat.com crond[2164]: ((null)) Unauthorized SELinux context=system_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 file_context=system_u:object_r:system_cron_spool_t:s0 (/etc/crontab)
Apr 25 08:34:14 gigabyte-r120-15.khw3.lab.eng.bos.redhat.com crond[2164]: (root) FAILED (loading cron table)

Expected results:
/etc/crontab should be loaded

Additional info:
ls -alZ /etc/crontab 
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 502 Nov  8 07:09 /etc/crontab

when I use "user_cron_spool_t" it loads well. I haven't set the "system_cron_spool_t" so I guess it's the default.

Any news about this? Is it expected behaviour or bug?

This is a duplucate of #1708557, please see that bug for more information and to track the progress.

*** This bug has been marked as a duplicate of bug 1708557 ***