Description of problem:

Crond is started before sssd, so there are no remote users defined yet.
Crond, as always, checks for crontab files in /var/spool/cron, but ignores 
files of non-existent users: i.e.: all non-local users. These files are
not considered again when remote users become available.

Cron logs something like:

Jun 15 12:37:52 cv04 kernel: [   16.411306] /usr/sbin/crond[685]: (visit3d) ORPHAN (no passwd entry)

So crond is started way too early by systemd; it should start after network 
users are defined (and even after network home directories are available,
as there is possibly an @reboot in the crontab).

Version-Release number of selected component (if applicable):

How reproducible:

Always

Steps to Reproduce:
1. Have non-local users (LDAP, NIS, whatever).
2. Have such a user make a crontab
3. Reboot
  
Actual results:

The users' crontab is ignored.

Expected results:

Crontab to function as it used to.

Additional info:

Don't really know if this is to be filed against cronie or systemd, because
cron is indeed started too early, but a robust cron should not expect the
user list to remain static forever neither...