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.

Created attachment 436581 [details]
yum update log

I'm taking a guess here at the component since ypbind wasn't involved in the yum transaction.

Description of problem:
I was logged in (authenticated with NIS), did a yum upgrade and after it finished `whoami` couldn't figure out who I was.

Version-Release number of selected component (if applicable):
sssd-client.x86_64 0:1.2.1-23.el6

How reproducible:
Unknown

Steps to Reproduce:
1. Install beta2, set up NIS and log in that way
2. yum update
  
Actual results:
/etc/init.d/ypbind restart required to make `whoami` work (and not give errors about username not found for UID #)

Expected results:
No changes required with authentication

Additional info:

This is a duplicate of BZ607233

It's actually fixed in the version that you upgraded TO, but since ypbind at the time already had the older library loaded, it couldn't cope with the SSSD having been restarted.

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

Thanks for the info, Stephen.