Bug 913280

Summary:	sssd.service not enabled when using enterprise login in gnome-shell gui
Product:	[Fedora] Fedora	Reporter:	Joël Wijngaarde <wijngaarde>
Component:	sssd	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	jhrozek, kyle, pbrezina, sbose, sgallagh, ssorce, stefw
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-17 12:08:44 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 Joël Wijngaarde 2013-02-20 19:54:46 UTC

Description of problem:
When add a user using the gnome-shell user dialog from the settings UI for the first time the system correctly starts the sssd.service. Wen you reboot the service the sssd.service is not enabled. Looks like the sssd.service is started but not enabled (ie. systemctl enable sssd.service).

Version-Release number of selected component (if applicable):
This happens using a fresh DVD install of Fedora 18 after a yum update.

How reproducible:
Did it on two different workstations, both had the same problem.

Steps to Reproduce:
1. Install Fedora 18 DVD
2. Add AD enterprise user using system user dialog provided by gnome-shell
3. Test if you can login (should work)
4. reboot
5. test if you can login, this time it should not work
  
Actual results:
You cannot login after a reboot

Expected results:
Login using AD credentials on machine

Additional info:
After starting the sssd.service login works. It looks like the sssd.service is not automatically enabled only started when adding Enterprise users to the system.

Comment 1 Jakub Hrozek 2013-02-20 20:55:40 UTC

Joel, have you checked if the sssd service is actually enabled or if it failed to start for some other reason?

Stef, does the realmd also enable the systemd service or does it just call authconfig and relies on authconfig doing it?

Comment 2 Joël Wijngaarde 2013-02-21 09:24:17 UTC

Before adding an enterprise user the sssd package was not installed on my system. When I added the first enterprise user the sssd package was installed on my system in the background. A dialog appeared asking me to join the AD domain. After this the user was successfully added.

When I check on the terminal the status of the sssd.service:

$ systemctl status sssd.service

It shows the service is running but *NOT* enabled. After a reboot when I check again the status it says the sssd.service is dead. After I start the service I can login using the enterprise account:

$ systemctl start sssd.service

Enabling the service fixes the reboot issue

$ systemctl enable sssd.service

So I do not think there is an error when it tries to start the service. The only point to note is that the sssd package was not installed on my system(s) by default.

Comment 3 Jakub Hrozek 2013-04-17 12:08:44 UTC

I'm quite certain this is a duplicate of #952844 which was fixed recently in realmd.

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

Comment 4 Kyle Strickland 2013-04-19 12:39:56 UTC

I don't think this is a duplicate of bug 952844, unless the race described there prevents the sssd service from being configured to start on boot.

I'm having the same problem that Joël Wijngaarde described, but using the command line "realm" program.  After running "realm join ...", the sssd service is "started" successfully, but the problem comes after rebooting, since the service is not "enabled" in systemd--that is, it is not configured to start up when you boot.

So after doing the first "realm join ..." and "realm permit ...", I can log in and life is good.  Until the next time I reboot.  Then, when I try to log in the system has no idea who I am.

The fix would seem to be to add the equivalent of "systemctl enable sssd.service" to the realm-join action, whereas right now it only performs the equivalent of "systemctl start sssd.service".

Comment 5 Stef Walter 2013-04-19 12:42:13 UTC

realmd does 'systemctl enable sssd.service'. 

Could you list the version of realmd you have installed?

Comment 6 Stef Walter 2013-04-19 12:43:43 UTC

This may be related to: https://bugzilla.redhat.com/show_bug.cgi?id=953851

Comment 7 Kyle Strickland 2013-04-19 13:02:08 UTC

realmd-0.12-1.fc18.x86_64