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

[Eric Desrochers]

** Description changed:

  [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
  ```

-- 
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:
  In Progress

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