[Bug 1695870] Re: [regression] sssd won't start if autofs is not installed

Fri Jul 14 08:55:39 UTC 2017

#VERIFICATION FOR XENIAL+Upstart (LP#1695870)

- Version of the package: 1.13.4-1ubuntu1.6

ubuntu at xenial-upstart:~$ dpkg -l | grep sssd
ii  sssd                              1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- metapackage
ii  sssd-ad                           1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- Active Directory back end
ii  sssd-ad-common                    1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- PAC responder
ii  sssd-common                       1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- common files
ii  sssd-ipa                          1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- IPA back end
ii  sssd-krb5                         1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- Kerberos back end
ii  sssd-krb5-common                  1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- Kerberos helpers
ii  sssd-ldap                         1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- LDAP back end
ii  sssd-proxy                        1.13.4-1ubuntu1.6                          amd64        System Security Services Daemon -- proxy back end

- After installing sssd from -proposed in a machine without autofs, sssd
starts automatically after a reboot:

# confirmation of autofs not installed:
ubuntu at xenial-upstart:~$ dpkg -l | grep -i autofs
ubuntu at xenial-upstart:~$ ls /etc/init/aut*
ls: cannot access /etc/init/aut*: No such file or directory
ubuntu at xenial-upstart:~$ ls /etc/init.d/aut*
ls: cannot access /etc/init.d/aut*: No such file or directory

ubuntu at xenial-upstart:~$ 
Broadcast message from ubuntu at xenial-upstart
        (/dev/pts/0) at 11:03 ...

The system is going down for reboot NOW!

...

Last login: Wed Jul 12 11:02:45 2017 from 10.5.1.55
ubuntu at xenial-upstart:~$ status sssd
sssd start/running, process 1109

ubuntu at xenial-upstart:~$ ps -ef | grep sss
root      1109     1  0 11:03 ?        00:00:00 sssd -D -f
root      1126  1109  0 11:03 ?        00:00:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain openstacklocal --uid 0 --gid 0 --debug-to-files
root      1164  1109  0 11:03 ?        00:00:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_nss --uid 0 --gid 0 --debug-to-files
root      1165  1109  0 11:03 ?        00:00:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_pam --uid 0 --gid 0 --debug-to-files
root      1166  1109  0 11:03 ?        00:00:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_autofs --uid 0 --gid 0 --debug-to-files
ubuntu    1546  1530  0 11:05 pts/0    00:00:00 grep --color=auto sss

- And from /var/log/syslog:

...
Jul 12 11:03:39 xenial-upstart kernel: [    9.028635] audit: type=1400 audit(1499857419.712:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=950 comm="apparmor_parser"
Jul 12 11:03:39 xenial-upstart dbus[953]: [system] AppArmor D-Bus mediation is enabled
Jul 12 11:03:39 xenial-upstart pollinate[892]: system was previously seeded at [2017-03-06 18:34:25.400000000 +0000]
Jul 12 11:03:39 xenial-upstart pollinate[892]: To re-seed this system again, use the -r|--reseed option
Jul 12 11:03:39 xenial-upstart kernel: [    9.136051] Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
Jul 12 11:03:40 xenial-upstart sssd: Starting up
Jul 12 11:03:40 xenial-upstart sssd[be[openstacklocal]]: Starting up
Jul 12 11:03:40 xenial-upstart sssd[nss]: Starting up
Jul 12 11:03:40 xenial-upstart sssd[pam]: Starting up

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1695870

Title:
  [regression] sssd won't start if autofs is not installed

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Trusty:
  Fix Released
Status in sssd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * On Trusty, SSSD does not start when AutoFS is not installed because the AutoFS "starting" signal is not emitted.
   * This only affects the upstart service (Trusty). Systemd services work fine.

  [Test Case]

   * Install SSSD in a machine without AutoFS and reboot.
   * The service won't start on boot, even though it can be started manually.

  [Regression Potential]

   * None expected, but if one is found it will only impact the startup
  of SSSD at boot

  [Original Description]

  * The Xenial regression has been first reported via LP: #1700084 and
  then we marked it a duplicate and decided to continue the SRU via this
  bug (being the original one) for the SRU to be less confusing.

  The fix for LP# 1566508 (in Ubuntu 14.04 at least) introduces a
  regression that prevents sssd from starting if the autofs package is
  not installed.

  The /etc/init/sssd.conf script now has:

  ```
  start on (filesystem and net-device-up and starting autofs)
  ```

  The "starting autofs" will never happen if autofs is not installed.

  That's critical in that that prevents authentication after the next
  boot after "sssd" has been upgraded.

  The work around for now is to remove that "and starting autofs" or
  install the autofs package.

  ```
  $ apt-cache policy sssd
  sssd:
    Installed: 1.11.8-0ubuntu0.6
    Candidate: 1.11.8-0ubuntu0.6
    Version table:
   *** 1.11.8-0ubuntu0.6 0
          500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       1.11.5-1ubuntu3 0
          500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1695870/+subscriptions