Comment # 4 on bug 1043466 from Jason Mader

y2log shows that the configuration isn���t run until,

2017-06-08 12:59:45 <1> linux(2813) [Ruby] clients/inst_autopost.rb:154 Calling
auto client with: $["sssd":"yes", "sssd_conf":$[...]]

which is after the first sssd startup,

Jun 08 12:59:28 linux sssd[973]: SSSD couldn't load the configuration database
[2]: No such file or directory.

2017-06-08 12:57:59 <1> install(4205) [Ruby] modules/Service.rb:112 Enabling
service 'sssd'
2017-06-08 12:57:59 <1> install(4205) [Ruby] yast2/systemd_unit.rb:122
`systemctl is-enabled sssd.service `
2017-06-08 12:57:59 <1> install(4205) [Ruby] yast2/systemd_unit.rb:122
`systemctl enable sssd.service `
2017-06-08 12:57:59 <3> install(4205) [bash] ShellCommand.cc(shellcommand):78
Created symlink from /etc/systemd/system/multi-user.target.wants/sssd.service
to /usr/lib/systemd/system/sssd.service.
2017-06-08 12:57:59 <1> install(4205) [Ruby] yast2/systemd_unit.rb:122
`systemctl is-enabled sssd.service `


It���s just that there���s no configuration file at that time.

On Leap 42.2 though,

2017-05-24 13:41:04 <1> linux(2460) [Ruby] clients/inst_autopost.rb:154 Calling
auto client with: $["sssd":"yes", "sssd_conf":$[...]]

the first startup after auto installation is,

-- Unit sssd.service has begun starting up.
May 24 13:41:21 linux sssd[6514]: Starting up