Ubuntu
sssd package

  1. Bug #1900642
  2. Comment #29

Comment 29 for bug 1900642

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Verification for Focal:

root@focal-desktop:~# apt policy sssd
sssd:
  Installed: 2.2.3-3ubuntu0.1
  Candidate: 2.2.3-3ubuntu0.1
  Version table:
 *** 2.2.3-3ubuntu0.1 500
        500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.2.3-3 500
        500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

Booting the VM and verifying that the bug exists:

root@focal-desktop:~# journalctl -u sssd.service --boot 0
Jan 15 13:20:14 focal-desktop systemd[1]: Starting System Security Services Daemon...
Jan 15 13:20:14 focal-desktop sssd[655]: SSSD couldn't load the configuration database [2]: No such file or directory.
Jan 15 13:20:14 focal-desktop systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
Jan 15 13:20:14 focal-desktop systemd[1]: sssd.service: Failed with result 'exit-code'.
Jan 15 13:20:14 focal-desktop systemd[1]: Failed to start System Security Services Daemon.
Jan 15 13:20:14 focal-desktop systemd[1]: sssd.service: Scheduled restart job, restart counter is at 1.
Jan 15 13:20:14 focal-desktop systemd[1]: Stopped System Security Services Daemon.
...

Installing the proposed package and verifying that it solves the problem:

root@focal-desktop:~# apt policy sssd
sssd:
  Installed: 2.2.3-3ubuntu0.2
  Candidate: 2.2.3-3ubuntu0.2
  Version table:
 *** 2.2.3-3ubuntu0.2 500
        500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     2.2.3-3ubuntu0.1 500
        500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
     2.2.3-3 500
        500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

root@focal-desktop:~# journalctl -u sssd.service --boot 0
-- Logs begin at Tue 2020-12-08 17:53:54 EST, end at Fri 2021-01-15 13:23:18 EST. --
Jan 15 13:23:07 focal-desktop systemd[1]: Condition check resulted in System Security Services Daemon being skipped.

Therefore, the service was correctly skipped because there is no configuration file present.

Verification done for Focal.