Bug 713413

Summary: cron does not work at all for non-local (LDAP, NIS, ...) users
Product: [Fedora] Fedora Reporter: Bert DeKnuydt <Bert.Deknuydt>
Component: cronieAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: mmaslano, pertusus, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: cronie-1.4.8-2.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-04 18:58:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Bert DeKnuydt 2011-06-15 10:52:49 UTC 
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...
Comment 1 Tomas Mraz 2011-06-15 12:23:30 UTC 
crond should be started as one of the latest services on boot.

Nevertheless I'll try to make cron periodically recheck whether the orphaned crontabs are not orphaned anymore.
Comment 2 Fedora Update System 2011-06-28 10:59:51 UTC 
cronie-1.4.8-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/cronie-1.4.8-1.fc15
Comment 3 Fedora Update System 2011-06-28 20:26:33 UTC 
Package cronie-1.4.8-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cronie-1.4.8-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/cronie-1.4.8-1.fc15
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2011-06-29 22:01:46 UTC 
Package cronie-1.4.8-2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cronie-1.4.8-2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/cronie-1.4.8-2.fc15
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2011-07-04 18:58:06 UTC 
cronie-1.4.8-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.