[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package sssd - 1.11.8-0ubuntu0.3 --- sssd (1.11.8-0ubuntu0.3) trusty; urgency=medium * d/p/fix-upstream-2519.diff SSSD should not fail authentication when only allow rules are used (LP: #1640805) -- Christian Ehrhardt

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-24 Thread ChristianEhrhardt
Per former comment, setting verification done ** 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/1640805 Title: SSSD authentication

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-24 Thread Florin Baca
Hi Robie, Thanks for the info, I have upgraded the proposed package on a broken system and I hereby confirm it solves the issue as expected. Current versions: sssd 1.11.8-0ubuntu0.3 sssd-ad 1.11.8-0ubuntu0.3 sssd-ad-common 1.11.8-0ubuntu0.3 sssd-common 1.11.8-0ubuntu0.3 sssd-ipa

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-23 Thread Robie Basak
Hello Florin, 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.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-22 Thread Timo Aaltonen
uploaded to the queue ** Also affects: sssd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-22 Thread ChristianEhrhardt
Sponsors seem to be very busy these days, I pinged Timo to hope we get this into Trusty Proposed sometime soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640805 Title: SSSD authentication

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-14 Thread ChristianEhrhardt
** Patch added: "debdiff fix for this issue" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1640805/+attachment/4777117/+files/fix-bug-1640805.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-14 Thread ChristianEhrhardt
Subscribing sponsors as I can't upload back to Trusty and given the mentioned weirdness on the packaging it is worth an extra eye to look at it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640805

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-14 Thread ChristianEhrhardt
Note for the SRU Review - something in the packaging here is odd (or it is me, the monday morning or something broken in the (my?) tooling) Please take an extra eye on the changes. I created a debdiff and tried all I could to make it a clean one, but I had hidden files/dirs sneak into them more

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-13 Thread ChristianEhrhardt
** Description changed: - During the first half of September, the Ubuntu sssd package has been - updated from 1.11.5-1ubuntu3 to 1.11.8-0ubuntu0.2. We use sssd for - authentication on a few dev servers and all our Ubuntu workstations. - After the first systems began upgrading we noticed people

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-13 Thread ChristianEhrhardt
Fixed in Ubuntu(dev) since Xenial, nominating for Trusty SRU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640805 Title: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2 To manage

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-11 Thread Bug Watch Updater
** Changed in: sssd Status: Unknown => 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/1640805 Title: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2 To manage

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-11 Thread Timo Aaltonen
thanks, looks good.. go ahead with the sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640805 Title: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2 To manage notifications about

Re: [Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-11 Thread ChristianEhrhardt
On Fri, Nov 11, 2016 at 10:36 AM, Florin Baca <1640...@bugs.launchpad.net> wrote: > That was very fast Christian, thanks! I have just tested on a freshly > installed Ubuntu and I can confirm the new ppa package fixed the issue > Great - thanks for the fast verify as well. FYI I'm waiting for a

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-11 Thread Florin Baca
That was very fast Christian, thanks! I have just tested on a freshly installed Ubuntu and I can confirm the new ppa package fixed the issue: [ansible | CLIENTS] ssh username@x.x.x.143 username@x.x.x.143's password: Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-101-generic x86_64) *

[Bug 1640805] Re: SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2

2016-11-11 Thread ChristianEhrhardt
Thanks for your pre-analysis on this Florin. It seems it is an upstream issue - just as you pointed out with the linked ticket. And that matches exactly what you report (and makes sense that neither me nor you find one of the changes Ubuntu introduced to be related to the issue). IMHO this