Bug 829740

Summary:	Init script reports complete before sssd is actually working
Product:	Red Hat Enterprise Linux 6	Reporter:	Dmitri Pal <dpal>
Component:	sssd	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED ERRATA	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.4	CC:	grajaiya, jgalipea, nikolai.kondrashov, prc, rhbugzilla
Target Milestone:	rc	Keywords:	Regression, TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sssd-1.9.2-7.el6	Doc Type:	Bug Fix
Doc Text:	Cause: When the SSSD deamon was starting, the parent processes would quit right after spawning the child process, which was before the SSSD was actually functional Consequence: The initscripts print [OK] after the parent process terminates, which was before the SSSD was actually functional Fix: The parent process is not terminated until all the worker processes are up Result: When the initscripts print [OK] the admin can actually start using the SSSD.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 09:24:12 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:

Description Dmitri Pal 2012-06-07 13:18:43 UTC

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

I installed a rhel 6.2 system with the sshd Privilege-separated user account only in active directory and not in the system /etc/passwd file.  Under these conditions sshd which is supposed to run directly after sssd will not start.

Instead the following error is returned:
[  OK  ] sssd: [  OK  ]
Starting sshd: Privilege separation user sshd does not exist
[FAILED]

The system sssd version is sssd-1.5.1-66.el6_2.3.x86_64

Comment 1 RHEL Program Management 2012-07-10 06:12:39 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 RHEL Program Management 2012-07-11 02:06:11 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 Kaushik Banerjee 2012-10-18 15:29:41 UTC

Tested with sssd-1.9.2-3.el6

Re-opening the bug:

# /etc/init.d/sssd stop && rm -f /var/lib/sss/db/*.ldb /var/lib/sss/mc/* /var/log/sssd/* && /etc/init.d/sssd start && date && id kau1; sleep 3 && date && id kau1
Stopping sssd:                                             [  OK  ]
Starting sssd:                                             [  OK  ]
Thu Oct 18 20:57:50 IST 2012
id: kau1: No such user
Thu Oct 18 20:57:53 IST 2012
uid=1111(kau1) gid=1111(kau1_grp1) groups=1111(kau1_grp1)

Comment 7 Nikolai Kondrashov 2012-11-20 07:04:44 UTC

Verified in version 1.9.2-13.

Comment 8 Nikolai Kondrashov 2013-01-08 15:05:16 UTC

There is no specific test for this, but half of the sudo suite would fail if this is broken.

Comment 9 errata-xmlrpc 2013-02-21 09:24:12 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.

http://rhn.redhat.com/errata/RHSA-2013-0508.html