This bug was fixed in the package sssd - 1.13.4-1ubuntu1.6
---
sssd (1.13.4-1ubuntu1.6) xenial; urgency=medium
* Fix regression where SSSD doesn't start on boot if autofs is not
installed (LP: #1695870):
- rules: Support new service
- sssd-common.sssd-autofs.upstart.in: Restart autofs to read direct mounts
after SSSD and autofs have started (only on startup). This keeps the fix
for the autofs and SSSD race condition (LP: #1566508)
- sssd-common.sssd.upstart.in: Remove "starting autofs" to allow SSSD to
start without autofs.
-- Victor Tapia Mon, 05 Jun 2017 12:41:12
+0200
** Changed in: sssd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 Released
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
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
