This bug was fixed in the package sssd - 2.2.0-4ubuntu1
---
sssd (2.2.0-4ubuntu1) eoan; urgency=medium
* Merge with Debian unstable. Remaining changes:
- Switch sss_obfuscate shebang to python3.
* Dropped:
- Fix build with newer samba (4.10+):
+ d/p/build-newer-samba
See also bug 1838380. Perhaps these should all be merged into the same
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821927
Title:
Systemd do not respawn sssd on failure
To manage notificatio
On Thu, Aug 1, 2019 at 8:50 AM Robie Basak <1821...@bugs.launchpad.net> wrote:
>
> Surely if we're in agreement that we should be consistent, that means
> that we either patch to make them one way, or we patch to make them
> consistent the other way.
Umm this is derailing I think - the last time w
Surely if we're in agreement that we should be consistent, that means
that we either patch to make them one way, or we patch to make them
consistent the other way. Patching to make them inconsistent doesn't
follow, and nor does not patching an exception to leave that one
different from all the othe
In this case Robie we are following upstream where we suggested it due to this
bug.
And while I agree to making things consistent across packages we have talked
about it before and nothing happened yet. IMHO: It is correct to say "let us
use this as a reminder to reconsider an effort across pack
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/sssd/+git/sssd/+merge/370825
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821927
Title:
Systemd do not respawn ss
I'm not keen on doing something special just for sssd. Either all
"server-y" packages should be Restart=on-failure, or none of them, or we
should have clear criteria. It's the job of the distribution to provide
consistency across packages here.
--
You received this bug notification because you ar
** Changed in: sssd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
It seems this fell through the cracks, sorry for that.
While cleaning up bugs and tasks I found it and filed an upstream discussion
[1].
Depending on the outcome of this we can make the modification (or not).
[1]: https://pagure.io/SSSD/sssd/issue/4040
** Changed in: sssd (Ubuntu)
Assignee:
We discussed this yesterday and think that is a vlaid bug report - thanks!
It spawned a spin-off discussion how we want to handle auto-restart in general
which will go on for a while.
For this particular case Andreas wanted to take a look at the details and maybe
bring the suggestion also upstre
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821927
Title:
Systemd do not respawn sssd on failure
To manage notifications about this bug go to:
https://bugs
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821927
Title:
Systemd do not respawn sssd on failure
To manage notifications about this bug go to:
https://bugs.l
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/1821927
Title:
Syste
13 matches
Mail list logo
