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:
When switching from one NIS domain to another the NIS user cronjobs become ophaned saying that there is (no passwd entry). The getent and id commands both accurately produce the user's information. A restart of the crond service is required to get the cronjobs working again.

Both NIS domains have the same information, the user was just moving the NIS master to a different datacenter.



Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.4 (Santiago)
ypbind-1.20.4-30.el6.x86_64
cronie-1.4.4-7.el6.x86_64


How reproducible:
Switching NIS domain binding from one NIS domain to another NIS domain


Steps to Reproduce:
1. Prepare two NIS servers in your test lab for a NIS client to switch in between. 
2. Change the NIS domain binding

Actual results:

NIS user cronjobs do not run and produce the following errors for the NIS users

Oct 31 11:51:01 servername crond[####]: (username1) ORPHAN (no passwd entry)
Oct 31 11:51:01 servername crond[####]: (username2) ORPHAN (no passwd entry)


Expected results:

The cronjobs for the users keep working

Additional info:

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