LP: #1566508 looks like it's been resolved, and LP: #1614248 appears
still an issue in xenial but fixed in zesty and newer. LP: #1588915 is
still open but seems to be an ifupdown bug rather than autofs itself,
and has not been updated since 2017 and I'm not sure if it is still an
issue on newer re
Robie, thank you for your comment.
There is a number of bugs related to autofs and sssd present in Xenial. A
partial attempt to sort out this situation can be found in bug 1566508, comment
#20 (https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/comments/20 ).
However, this is compounded
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I uploaded a newer autofs to Zesty yesterday. This restores the systemd
service, which was previously being replaced by an upstart job. On
16.04, I suspect (but haven't checked) that this caused a fallback to
the i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: autofs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614282
Title:
aut
