Having this problem with freeipa on xenial.
ii sssd-ipa 1.13.4-1ubuntu1.8
amd64System Security Services Daemon -- IPA back end
--- client side output ---
alvinc@ipa-client-02:~$ sudo systemctl restart autofs
[sudo] password for alvinc:
alvinc@ipa-client-02:~$ su
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about this bug go to:
https://bugs.lau
** Tags removed: verification-done
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications abo
This bug was fixed in the package sssd - 1.11.8-0ubuntu0.7
---
sssd (1.11.8-0ubuntu0.7) trusty; 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:
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about th
# VERIFICATION FOR TRUSTY (LP#1566508)
- Version of the package: 1.11.8-0ubuntu0.7
$ ssh vtapia-trusty "dpkg -l | grep -i sssd"
Warning: Permanently added 'vtapia-trusty,10.5.1.100' (ECDSA) to the list of
known hosts.
ii libsss-idmap0 1.11.8-0ubuntu0.7
reopening for trusty, since this fix regressed non-autofs case
** Changed in: sssd (Ubuntu Trusty)
Status: Fix Released => In Progress
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
LP #1695870 will address this regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about this bug go to:
https://bugs.la
The fix in 14.04 causes sssd to not start on boot when "autofs" is not
installed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notificati
This bug was fixed in the package sssd - 1.11.8-0ubuntu0.6
---
sssd (1.11.8-0ubuntu0.6) trusty; urgency=medium
* d/p/pidfile-creation.diff: Delay the pidfile creation until the
responders are up (LP: #1566508)
* d/p/sanitize_newline.diff: Sanitize newline and carriage return
#VERIFICATION FOR TRUSTY (1.11.8-0ubuntu0.6)
Script from #46, excerpt of the logs:
Warning: Permanently added 'vtapia-trusty,10.5.1.100' (ECDSA) to the list of
known hosts.
May 25 15:46:01 vtapia-trusty sssd: Starting up
May 25 15:46:01 vtapia-trusty sssd[be[openstacklocal]]: Starting up
May 25
Hello Maciej, or anyone else affected,
Accepted sssd into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sssd/1.11.8-0ubuntu0.6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
This bug was fixed in the package sssd - 1.13.4-3ubuntu0.4
---
sssd (1.13.4-3ubuntu0.4) yakkety; urgency=medium
* d/p/pidfile-creation.diff: Delay the pidfile creation until the
responders are up (LP: #1566508)
* d/p/sanitize_newline.diff: Sanitize newline and carriage return
This bug was fixed in the package sssd - 1.13.4-1ubuntu1.5
---
sssd (1.13.4-1ubuntu1.5) xenial; urgency=medium
* d/p/pidfile-creation.diff: Delay the pidfile creation until the
responders are up (LP: #1566508)
* d/p/sanitize_newline.diff: Sanitize newline and carriage return
#VERIFICATION FOR YAKKETY (1.13.4-3ubuntu0.4)
Script from #46, excerpt of the logs:
May 3 16:04:37 vtapia-yakkety sssd: Starting up
May 3 16:04:37 vtapia-yakkety sssd[be[openstacklocal]]: Starting up
May 3 16:04:38 vtapia-yakkety sssd[pam]: Starting up
May 3 16:04:38 vtapia-yakkety sssd[autof
Sorry, I meant 1.13.4-1ubuntu1.5 for Xenial:
ubuntu@vtapia-xenial:~$ dpkg -l | grep sssd-common
ii sssd-common 1.13.4-1ubuntu1.5
amd64System Security Services Daemon -- common files
--
You received this bug notification because you are a m
#VERIFICATION FOR XENIAL (1.13.4-3ubuntu0.4)
Using the script in comment #46, I've had the machine rebooting for
several days without hitting the issue. This is an excerpt of the logs:
Warning: Permanently added 'vtapia-xenial,10.5.1.88' (ECDSA) to the list of
known hosts.
May 3 16:00:39 vtapia
I will be accepting the latest upload to -proposed but please be sure to
include *all* changes mentioned in the debian/changelog. One of the
previous uploads was missing the mention of the sssd-
common.sssd.upstart.in file being changed - this should be mentioned
along with the patch name.
** Tags
** Tags removed: verification-failed
** Tags added: verification-failed-xenial verification-failed-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on star
** Tags removed: verification-done-xenial verification-done-yakkety
verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races
I tested sssd-1.13.4-1ubuntu1.4, and after several reboot on xenial
distro I can confirm that the bug is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on
# VERIFICATION FOR YAKKETY
Using the same script for Yakkety, I can confirm that the fix works as
expected. This is the log after 1300 succesful reboots:
Warning: Permanently added 'vtapia-yakkety,10.5.1.90' (ECDSA) to the list of
known hosts.
Mar 31 08:40:31 vtapia-yakkety systemd[1]: Started L
I tested sssd-1.13.4-1ubuntu1.4 on xenial on a bare metal machine
equipped with Intel X550T, a network controller notorious for long and
somewhat random startup initialization time. I am happy to report that
autofs boot problems still occur, but at a much diminished rate. While
previously autofs wa
# VERIFICATION FOR XENIAL
I prepared a reproducer based on the description details (LDAP + NFS)
using an entry_cache_timeout of 88000 in sssd.conf to ensure the cache
was valid during the validation run. From a remote machine, I ran this
script:
#!/bin/bash
OK=0
KO=0
while true ; do
#date
nova r
Hello Maciej, or anyone else affected,
Accepted sssd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sssd/1.13.4-1ubuntu1.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
** Tags removed: sts-sru
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about this bug go to:
h
Hi Maciej,
After a verification run, I can confirm that it still fails for . I'll
update my fixes and upload them again.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: sssd (Ubuntu Trusty)
Status: New => In Progress
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To
Here are the results on my tests of package sssd-1.13.4-1ubuntu1.3 on
Xenial.
As I noted in comment #20, this bug report involves two separate issues, both
contributing to failure of autofs to properly start on boot:
1. autofs starts before sssd.
2. autofs starts after sssd, but before sssd respo
I did brief testing of sssd-1.13.4-1ubuntu1.3 on Xenial. Autofs still
fails to properly start on boot, but I am not sure which of the numerous
issues described in this bug report contributes to the failure now. I
will do more testing after the weekend.
--
You received this bug notification becaus
Hello Maciej, or anyone else affected,
Accepted sssd into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sssd/1.13.4-3ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
** Changed in: sssd (Ubuntu Trusty)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: sssd (Ubuntu Xenial)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: sssd (Ubuntu Yakkety)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: sssd (Ubuntu
** Also affects: sssd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because yo
** Patch removed: "yakkety_sssd_1.13.4-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4811489/+files/yakkety_sssd_1.13.4-3ubuntu1.debdiff
** Patch removed: "trusty_sssd_1.11.8-0ubuntu0.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug
** Patch added: "yakkety-sssd_1.13.4-3ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4832800/+files/yakkety-sssd_1.13.4-3ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "trusty-sssd_1.11.8-0ubuntu0.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4832799/+files/trusty-sssd_1.11.8-0ubuntu0.6.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
For Ubuntuers dummies like me :)
activate xenial-proposed via https://wiki.ubuntu.com/Testing/EnableProposed to
install sssd_1.13.4-1ubuntu1.2 on xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hi
sorry for my lack of knowledge, but regarding comment #32, I'm waiting for a
fix in xenial repo.
It's seems to be present on the server
(http://fr.archive.ubuntu.com/ubuntu/pool/main/s/sssd/sssd_1.13.4-1ubuntu1.2_amd64.deb),
but probably not in the index of the mirror...
When will it be ava
This bug was fixed in the package sssd - 1.15.0-3ubuntu1
---
sssd (1.15.0-3ubuntu1) zesty; urgency=medium
* Build without the secrets service as libhttp-parser2.1 is in universe. An
MIR is pending in LP 1638957; when this is complete, we can revert this.
- Configure with --w
** Patch added: "trusty_sssd_1.11.8-0ubuntu0.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4811490/+files/trusty_sssd_1.11.8-0ubuntu0.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Tags added: sts-sponsor sts-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about this bug go to:
https://bugs.launchpa
** Patch added: "xenial_sssd_1.13.4-1ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4811491/+files/xenial_sssd_1.13.4-1ubuntu1.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Patch added: "yakkety_sssd_1.13.4-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4811489/+files/yakkety_sssd_1.13.4-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** No longer affects: autofs (Ubuntu)
** Changed in: sssd (Ubuntu)
Importance: Undecided => Critical
** Changed in: sssd (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Description changed:
+ [Impact]
+
+ * SSSD is set as started before its responders are active.
+ * Depending services (e.g. autofs) start before those responders are
working, and a manual restart is required to make them work after boot
+ * This happens with upstart and, with less frequen
** Changed in: autofs (Ubuntu)
Status: Confirmed => Invalid
** Changed in: sssd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Victor Tapia (vtapia)
--
You received this bug notification because you are a member of Ubuntu
Bugs
The patch was merged[1], so I'll start working in the SRU as soon as I
can.
https://git.fedorahosted.org/cgit/sssd.git/commit/?id=d4063e9a21a4e203bee7e0a0144fa8cabb14cc46
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Victor, thanks a lot for the explanation. I apologize for not
volunteering to test your patch, but it fixes an issue (#2) that I am
unable to reproduce in Xenial. But I really appreciate your efforts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hi Maciej,
I'm attaching the suggested patch to this bug, but bear in mind it's
adapted to upstream's code.
Originally, SSSD creates the pidfile at an early stage (once it forks)
before the providers have started. This patch moves the pidfile creation
to a point where the providers are up and rea
Victor, would you be so kind to post a link to your patch, and also tell
us which of the numerous issues discussed in this bug report (comment
#20) are solved by the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
A patch has been submitted upstream for review. As soon as it lands,
I'll work on an SRU.
Regards,
Victor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on sta
#23 works for me - fantastic
Thanks
Mal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about this bug go to:
https://bugs.l
I wasn't able to fix the issue with the solutions proposed up there,
so I managed to find another workaround for autofs to be operational on startup.
The only difference is that im using unbound to resolve my DNS.
Just add this line under EnvironnementFile in
/etc/systemd/system/multi-user.target.
> Is it a daft question to ask why it works for them and not you ?
This is a very good question. My take on it is as follows.
There are several issues here, and the majority are related to startup
configuration. Speaking of Ubuntu 16.04, the problem is that Ubuntu
first switched from SysV startup
We are experimenting with using a Debian based distro
and this bug seems to be in all of them. We currently use
OpenSUSE 13.2/Leap 42.1 and this works perfectly. Is it a
daft question to ask why it works for them and not you ?
Ta
M
--
You received this bug notification because you are a member
Here is my attempt to sort out how many bugs are related to autofs
failing on boot.
This bug (1566508)
As noted earlier, these are actually two issues:
1. autofs starts before sssd.
2. autofs starts after sssd, but before sssd responders are up.
On Trusty, I observed #1 and #2, and on Xenial I ob
Issues related to ifup and service files included in ifupdown package
are reported as bug 1588915.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To
In order to test whether the bug which is the subject of this bug report
(i.e. "no mounts in table", not "setautomntent") occurs in Xenial with
systemd, I created autofs.service as attached below. This way I could
dispense with /etc/init.d/autofs and directly control when autofs is
started. I can r
Here is the autofs.service file mentioned above.
** Attachment added: "autofs.service"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+attachment/4719398/+files/autofs.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Jakub, the "setautomntent" message occurs at the same time when autofs
fails to mount shares on startup. So, while itself it is not a bug and
nobody here suggests that the message should be silenced, it is
nonetheless one of the symptoms of the problem, which is caused most
likely by a number of in
The message "setautomntent: lookup(sss): setautomntent: No such file or
directory" is not indicative of any bug whasoever. It just means there
are no more entries in this maps.
But in general, I think the most systematic way forward for this kind of
startup races would be to socket-activate the re
Victor, you are right saying that we are dealing with more than one bug
here. It appears to me that we have 3 or 4 separate bugs all conspiring
to prevent autofs from starting in the configuration as described above.
I think that the "setautomntent" error message is a symptom of a
different bug tha
>5. The issue being subject of this bug report is very likely still present,
>though I was unable to
>reproduce it exactly. Unfixed issue #2 caused auto fs to fail with a different
>error message
>("setautomntent: lookup(sss): setautomntent: No such file or directory"),
>while fixed issue #2 hi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sssd (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/1566508
Title:
autof
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/1566508
Title:
aut
Jakub, thanks for the information.
Launchpad mangles the URL that you posted in an attempt to hide email addresses
from public view, here it is in an equivalent form that does not include '@':
https://lists.fedorahosted.org/archives/list/sssd-devel%40lists.fedorahosted.org/message/QKU5H4VUCIZ43LBJ
As long as there are any maps in the cache, these fixes should help:
https://lists.fedorahosted.org/archives/list/sssd-de...@lists.fedorahosted.org/message/QKU5H4VUCIZ43LBJTRPPK3XWL6CTQNQ4/
(but upstream didn't merge them yet)
--
You received this bug notification because you are a member of Ubu
I finally had a chance to test this issue in Ubuntu 16.04. In a setup
described as in the bug description above, autofs still won't start
correctly, and this is a result of the whole string of problems. Most of
them appear to be separate bugs, but I will list them here for
completeness:
1. ifup re
Yes. Systemd takes longer to set sssd as started, making the time window
smaller for the race condition to happen, but it can still appear when
the machine boots fast enough (VMs, for instance, show this issue
consistently)
--
You received this bug notification because you are a member of Ubuntu
so this is an issue with systemd too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage notifications about this bug go to:
https://bugs.launc
Bug opened upstream: https://fedorahosted.org/sssd/ticket/3080
** Bug watch added: fedorahosted.org/sssd/ #3080
https://fedorahosted.org/sssd/ticket/3080
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "sssd.conf workaround for upstart"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+attachment/4688591/+files/sssd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
As mentioned in the description, Autofs starts before SSSD's responders
are running, even though SSSD is set to start before Autofs, both in
upstart and systemd. The problem is related to the boot process of SSSD
because upstart/systemd determine the job as started right after sssd
forks, when in r
** Tags added: sts
** Also affects: sssd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To mana
** Patch added: "autofs.conf.diff"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+attachment/4625148/+files/autofs.conf.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
T
75 matches
Mail list logo
