I can confirm that this bug also affects *some* of our desktops running
18.04. I haven't figured out why it didn't affect all (100+) machines.
Here is the status output of firewalld service running on a hostname
'matht335':
```
# systemctl status firewalld
The package sssd also add the autofs checking to /etc/init/sssd.conf in
Ubuntu 16.04 package. The only reason Ubuntu 16.04 wasn't affected is
because it uses systemd instead of upstart in Ubuntu 14.04.
Here is my temporary solution if you use Puppet to manage your systems:
class sssd::config {
Public bug reported:
After upgrading sssd, sssd-* from 1.11.8-0ubuntu0.5 to
1.11.8-0ubuntu0.6, sssd service no longer starts on boot.
According to the diff, it seems that checking 'autofs' was added to
/etc/init/sssd.conf. All our systems do not have autofs installed. This
may explain why sssd se
