We found a bug[0] on cron + selinux-policy that broke /etc/cron.d readability for cron, resulting in a non working /etc/cron.d directory and was proposed as blocker bug.
During the blocker-review meeting, there was a majority of attendes in favour of blocking due to this bug but we didn't have a clearly violated criteria [1], so I'd like to discuss about a new server criteria to fix this situation.
Let start with something short: "Cron service must work on server for root's jobs, other users' jobs and jobs from cron job directories inside /etc".
Actually is quite difficult to fully test cron funcionality (openqa worker can't wait for 3 months to see if cron is working properly for a trimestral cron line), so I think that we should be more specific about "must work".
Regards,
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1625645 [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-09-24/f29-b...