Disco has this fixed already, updating main task.
** Changed in: sssd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1807246
Title:
Disco has this fixed already, updating main task.
** Changed in: sssd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after
This bug was fixed in the package sssd - 1.16.1-1ubuntu1.1
---
sssd (1.16.1-1ubuntu1.1) bionic; urgency=medium
* d/p/fix-id-out-of-range-lookup.patch: CACHE_REQ: Do not fail the domain
locator plugin if ID outside the domain range is looked up. Thanks to
Jakub Hrozek .
Bionic verification
First, confirming the bug:
# checking ldap user exists, and is not defined in /etc/passwd
root@bionic-sssd-1807246:~# id testuser1
uid=10001(testuser1) gid=10001 groups=10001,10100
root@bionic-sssd-1807246:~# grep testuser1 /etc/passwd
root@bionic-sssd-1807246:~#
# looping
Bionic verification
First, confirming the bug:
# checking ldap user exists, and is not defined in /etc/passwd
root@bionic-sssd-1807246:~# id testuser1
uid=10001(testuser1) gid=10001 groups=10001,10100
root@bionic-sssd-1807246:~# grep testuser1 /etc/passwd
root@bionic-sssd-1807246:~#
# looping
luke@schierer@talemludum001:~$ dpkg -l | grep sss
ii libnss-sss:amd64 1.16.1-1ubuntu1 amd64
Nss library for the System Security Services Daemon
ii libpam-sss:amd64 1.16.1-1ubuntu1 amd64
Pam module for the
Hello Luke, or anyone else affected,
Accepted sssd into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sssd/1.16.1-1ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
When the max_id parameter is used in an sssd [domain], and a lookup is
performed for a user with an id higher than that, and the cache expired, sssd
fails to query that user in the other defined domains.
The fix explicitly checks for the max_id case,
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/sssd/+git/sssd/+merge/361848
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to
** Description changed:
[Impact]
When the max_id parameter is used in an sssd [domain], and a lookup is
performed for a user with an id higher than that, and the cache expired, sssd
fails to query that user in the other defined domains.
The fix explicitly checks for the max_id case,
** Description changed:
[Impact]
+ When the max_id parameter is used in an sssd [domain], and a lookup is
performed for a user with an id higher than that, and the cache expired, sssd
fails to query that user in the other defined domains.
- * An explanation of the effects of the bug on
** Description changed:
[Impact]
+ When the max_id parameter is used in an sssd [domain], and a lookup is
performed for a user with an id higher than that, and the cache expired, sssd
fails to query that user in the other defined domains.
- * An explanation of the effects of the bug on
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * An explanation of the effects of the bug on users and
- * justification for backporting the fix to the stable release.
+ * justification for backporting the fix to the stable release.
-
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * An explanation of the effects of the bug on users and
- * justification for backporting the fix to the stable release.
+ * justification for backporting the fix to the stable release.
-
** Description changed:
- I configured sssd on an Ubuntu 16.04 LTS system, and it worked just
- fine. In fact, using the same sssd.conf file (which is managed by
- puppet) on un-upgraded system continues to work fine.
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+
** Description changed:
- I configured sssd on an Ubuntu 16.04 LTS system, and it worked just
- fine. In fact, using the same sssd.conf file (which is managed by
- puppet) on un-upgraded system continues to work fine.
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+
Problem reproduced, and also verified that the test packages fix it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I am
Problem reproduced, and also verified that the test packages fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I am frequently
Building test packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I am frequently
To manage notifications about this bug go to:
Building test packages.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I am frequently
To manage notifications about this
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
** Changed in: sssd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
** Changed in: sssd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Changed in: sssd (Ubuntu)
Status: Incomplete => Triaged
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session
any word on getting the fix merged into ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I am frequently
To manage
confirmed that not having a max_id line in the local domain does work
around the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets
FYI: fix is [1] in PR [2]
@Andreas will you take a look at that when you are back?
[1]: https://pagure.io/SSSD/sssd/c/2952de7
[2]: https://github.com/SSSD/sssd/pull/565
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
upstream says there is a known problem with having a domain with max_id
set in the version that bionic ships. This is apparently covered in
https://pagure.io/SSSD/sssd/issue/3728
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you Luke!
Lets see if there is any new update that might shed some light here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I
https://pagure.io/SSSD/sssd/issue/3900
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807246
Title:
after upgrading to bionic, my session forgets who I am frequently
To manage notifications about
That is odd, AFAIK Ubuntu didn't make any changes on top of upstream in that
regard.
So the only thing that comes to my mind would be an intentional upstream change
bweteen the sssd versions in 16.04 (1.13.4-1ubuntu1.12) and 18.04
(1.16.1-1ubuntu1)
@Luke
Would you mind filing an upstream bug
I changed enum_cache_timeout to 600 and set entry_cache_timeout = 200 in
the [domain/schierer] section of the above sssd.conf file. Despite
that, it still starts stating I am unknown around 320 seconds ( I have
316 seconds worth of successful "whoami ; sleep 10s" loop iterations, I
know it took a
actually, that is right on 300, isn't it? anyway, as I said, while I
will manipulate the cache values, it shouldn't be necessary. This is a
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have verified there is no overlap in UIDs, so I don't think the
linuxquestions.org problem applies.
it apparently forgets a lot faster than I was realizing, I just don't
use commands that matter fast enough to notice:
```
luke@schierer@talemludum001:~$ !id
id luke@schierer
Hi the only thing that comes to my mind would be the default values of
the enumeration cache timeouts. those are in the 2-5 minute range.
Check [1] for enum_cache_timeout and related entries.
Maybe create a script that does "while true; sleep 10s; date; check UID; done"
Then you can check how
34 matches
Mail list logo
