Bug 1332089

Summary: winbindd does not reuse sealed ldap connections
Product: Red Hat Enterprise Linux 6 Reporter: Rik Theys <rik.theys>
Component: samba4Assignee: Guenther Deschner <gdeschner>
Status: CLOSED WONTFIX QA Contact: Kaleem <ksiddiqu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6CC: asn, jarrpa, nlevinki, rhs-smb, rnalakka, sbose, storage-qa-internal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1331763 Environment:
Last Closed: 2017-11-21 09:34:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rik Theys 2016-05-02 08:07:07 UTC 
Hi,

This bug also affects RHEL6 with samba4 packages since they were upgraded to 4.2.10 (badlock bug).

Upstream has a patch for this.

Regards,

Rik

+++ This bug was initially created as a clone of Bug #1331763 +++

Description of problem:

/var/log/messages fills with  below error messges

winbindd[xxxx]:   gss_init_sec_context failed with [Unspecified GSS failure.  Minor code may provide more information: Ticket expired]

After winbind packages upgraded to -4.2.11-2, in a RHGS 3.1 node that is integrated with Active Directory . 


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

Red Hat Gluster Storage 3.1
samba-winbind-4.2.11-2.el6rhs.x86_64

How reproducible:

Always. 

Steps to Reproduce:
1. Install RHGS 3.1 with samba-windbind-4.2.11-2
2. Integrate with Active Directory 
3. Check the /var/log/messages. 

Actual results:

winbindd[xxxx]:   gss_init_sec_context failed with [Unspecified GSS failure.  Minor code may provide more information: Ticket expired]

Above messages in the /var/log/messages , since windbind not know  when to get a new krb5 ticket since a regression in the mentioned package. 


Expected results:

windbind handle session expiry properly and avoid the warning message. 



Additional info:

upstream samba BZ 

https://bugzilla.samba.org/show_bug.cgi?id=11852

upstream patch : https://git.samba.org/?p=samba.git;a=commitdiff;h=aec25b0cc232286c3e4d85de7f00483c09f7c66e

Thanks to Günther Deschner for helping wiith the above details.