Bug 1361567

Summary:	ldap_child does not remove temporary files when it's killed with SIGTERM
Product:	Red Hat Enterprise Linux 7	Reporter:	Jakub Hrozek <jhrozek>
Component:	sssd	Assignee:	Petr Čech <pcech>
Status:	CLOSED ERRATA	QA Contact:	Amith <apeetham>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	apeetham, grajaiya, jhrozek, lslebodn, mkosek, mzidek, pbrezina, sssd-qe
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sssd-1.15.0-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1415785 (view as bug list)		Environment:
Last Closed:	2017-08-01 08:58:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1415785

Description Jakub Hrozek 2016-07-29 12:22:53 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/3106

The ldap_child helper process creates a temporary file and then acquires credentials, which is a synchronous operation. If that takes more than a configured timeout, the parent (sssd_be) kills the child process with SIGTERM. But if the child process is killed, we don't remove the temporary file. We need to fix that..

Comment 2 Jakub Hrozek 2016-08-17 14:24:00 UTC

master:
    864cdac4c7fbe768d768da5e01b7518eb02836d9
    b9a0959c274367dcf69bba6b0a942a1682c74f73
    4313147ab4214037900cbb3ced8a03e492bff02c 
sssd-1-13:
    41afbb6b86d592be2d0f831dbea4f4d92b73cdb5
    09403b66fa73d294f38ddd4afa4d32eaf8d92087
    96e135a1b42c565c257e525c1eb04751058e6836

Comment 4 Amith 2017-06-01 12:22:58 UTC

Verified Sanity only on SSSD Version: sssd-1.15.2-37.el7.x86_64

Following automated test suites cover ldap_child & ldap_sasl_authid:

LDAP-KRB tests : https://beaker.engineering.redhat.com/jobs/1883216
AD provider ldap-krb tests: https://beaker.engineering.redhat.com/jobs/1883386

Comment 5 errata-xmlrpc 2017-08-01 08:58:07 UTC

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/RHEA-2017:2294