Your message dated Thu, 15 Feb 2018 13:56:31 +0200
with message-id <dc1b2563-c515-1047-c3e4-674de2f22...@debian.org>
and subject line Re: [Pkg-sssd-devel] Bug#890467: sssd: upgrade from 1.16.0-3
to 1.16.0-5 causes total failure of sssd to work, can not log into machine
has caused the Debian Bug report #890467,
regarding sssd: upgrade from 1.16.0-3 to 1.16.0-5 causes total failure of sssd
to work, can not log into machine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
890467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sssd
Version: 1.16.0-3
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
I had a working system with sssd providing my users and authentication
using an openldap and kerberos backend. I upgraded from 1.16.0-3 to
1.16.0-5 and the system could not find any users or allow anyone to
login.
I downgraded sssd an associated packages to 1.16.0-3 and rebooted, all
services were fully restored
Please note, the problem also occurred when I tried to install a brand
new machine based on stable, and then dist-upgraded it to current
testing, which pulled in sssd 1.16.0-5
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (750, 'testing'), (500, 'unstable'), (500, 'stable'),
(102, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sssd depends on:
ii python3-sss 1.16.0-3
ii sssd-ad 1.16.0-3
ii sssd-common 1.16.0-3
ii sssd-ipa 1.16.0-3
ii sssd-krb5 1.16.0-3
ii sssd-ldap 1.16.0-3
ii sssd-proxy 1.16.0-3
sssd recommends no packages.
sssd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 15.02.2018 00:59, Daniel Lakeland wrote:
>
> Package: sssd
> Version: 1.16.0-3
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I had a working system with sssd providing my users and authentication
> using an openldap and kerberos backend. I upgraded from 1.16.0-3 to
> 1.16.0-5 and the system could not find any users or allow anyone to
> login.
>
>
> I downgraded sssd an associated packages to 1.16.0-3 and rebooted, all
> services were fully restored
>
> Please note, the problem also occurred when I tried to install a brand
> new machine based on stable, and then dist-upgraded it to current
> testing, which pulled in sssd 1.16.0-5
You need to fix your config, 1.6.0-3 was what enabled responder services
and files domain, both of which were reverted since because they're not:
a) meant for Debian
and/or
b) properly tested upstream
-5 has now been in testing for two weeks without anyone else complaining.
--
t
--- End Message ---
