Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAndreas Schneider
2019-11-25 13:12:25 UTC
This bug was initially created as a copy of Bug #1657349
I am copying this bug because:
Description of problem:
All winbind authentication fails after updating to RHEL 7.6 immediately after winbind itself is updated.
Version-Release number of selected component (if applicable):
How reproducible:
customer has multiple servers to update and it has occurred on everyone so far
Steps to Reproduce:
1.start a looped ssh command
2.start the updating process
3.when winbind is updated the ssh connections will start to fail
Actual results:
ssh start to fail
Expected results:
winbind not to loose it's file links after update
Additional info:
From two lsof's before and after update:
$ grep libreplace-samba4 samba_bug_before.txt | grep winbindd
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
winbindd 2023 root mem REG 253,0 11088 101033174 /usr/lib64/samba/libreplace-samba4.so
winbindd 2024 root mem REG 253,0 11088 101033174 /usr/lib64/samba/libreplace-samba4.so
winbindd 2034 root mem REG 253,0 11088 101033174 /usr/lib64/samba/libreplace-samba4.so
winbindd 7268 root mem REG 253,0 11088 101033174 /usr/lib64/samba/libreplace-samba4.so
winbindd 9198 root mem REG 253,0 11088 101033174 /usr/lib64/samba/libreplace-samba4.so
$ grep libreplace-samba4 samba_bug_after.txt | grep winbindd
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
winbindd 1458 root DEL REG 253,0 101033174 /usr/lib64/samba/libreplace-samba4.so;5c0978f1
winbindd 1465 root DEL REG 253,0 101033174 /usr/lib64/samba/libreplace-samba4.so;5c0978f1
winbindd 1468 root DEL REG 253,0 101033174 /usr/lib64/samba/libreplace-samba4.so;5c0978f1
winbindd 20873 root DEL REG 253,0 101033174 /usr/lib64/samba/libreplace-samba4.so;5c0978f1
winbindd 20875 root DEL REG 253,0 101033174 /usr/lib64/samba/libreplace-samba4.so;5c0978f1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:1878