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,
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
