Closed robert4man closed 7 years ago
Now that I look and think about this a little more I'm thinking maybe this construct is a little too basic: class { '::sssd::config': } ~> class { '::sssd::service': } ->
sssd.conf changes should only trigger sssd service restarts, not everything.
I can agree with that. The other services were added b/c they were needed by sssd, but they def do not need restarted when config changes happen.
Fixed in 0.4.1
When upgrading from v0.3.0 -> v0.4.0 I encountered a couple odd issues. It looks like sssd.conf received some extra line spacing to separate the sections (which is fine) resulting in a restart of messagebus, sssd and oddjobd (which also seems fine). Unfortunately it resulted in a couple error conditions for RHEL7:
I was able to resolve both issues with systemctl restart systemd-logind NetworkManager. I was able to reproduce the issue manually with systemctl restart messagebus sssd oddjobd so this may be a system related bug/error. I'm not sure if there is even anything we could do from a puppet module perspective to deal with this condition, but I thought you should be aware.