I'm wondering if an sssd problem I've encountered is a 411 issue. I've already applied the 411 fix, but the problem persists.
In the post-installation section of my extend-compute.xml file sssd gets enabled ...
/usr/sbin/authconfig --enablesssd --enablesssdauth --update
... but following the automatic reboot, sssd.service fails to start, complaining that "sssd.conf does not exist":
[root@a32 ~]# systemctl status sssd
* sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/sssd.service.d
`-journal.conf
Active: failed (Result: exit-code) since Fri 2017-10-06 11:42:08 PDT; 24min ago
Main PID: 859 (code=exited, status=4)
Oct 06 11:42:07 a32.local systemd[1]: Starting System Security Services Daemon...
Oct 06 11:42:08 a32.local sssd[859]: Configuration file: /etc/sssd/sssd.conf does not exist.
Oct 06 11:42:08 a32.local systemd[1]: sssd.service: main process exited, code=exited, status=4/NOPERMISSION
Oct 06 11:42:08 a32.local systemd[1]: Failed to start System Security Services Daemon.
Oct 06 11:42:08 a32.local systemd[1]: Unit sssd.service entered failed state.
Oct 06 11:42:08 a32.local systemd[1]: sssd.service failed.
The file is getting pushed to the node via 411 as desired, and the timestamp matches that of the sssd startup error:
[root@a32 ~]# ls -al /etc/sssd/sssd.conf
-rw------- 1 root root 913 Oct 6 11:42 /etc/sssd/sssd.conf
Any idea what might be going wrong?