I found the culprit and thought I would post the update for posterity's 
sake.  Tailing the /var/log/messages file on the managed rhel6 host I 
noticed that sssd was starting, but authconfig was running after the 
startup and you see sssd shut down.  I reversed the order of my handlers 
file so that the authconfig handler ran first, and then the restart of my 
sssd service.  It is working now.

I had all sorts of code to show you, but google groups wont let me post it 
for some reason.

On Wednesday, November 8, 2017 at 3:17:49 PM UTC-7, John Harmon wrote:
>
> I have a playbook that configures ldap for linux servers via sssd.  It 
> runs against OEL 6, 7 and RHEL 6.  One OEL sssd is enabled and running when 
> the playbook is done; however, on RHEL6 the service is only enabled and not 
> running.  I can start the service without incident and it works as 
> expected.  Have any of you seen something similar?  I have been watching it 
> via logs and verbose output, but I can't find anything to tell me why it 
> isn't running on RHEL6.  I am assuming it is some type of a race issue.  
> Maybe I will put in a pause in my ansible playbook to see if that helps.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/942f087b-34b2-4ef1-b41f-ed60d328865c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to