Comment 30 for bug 1900642

Verification for Groovy.

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

Booting the VM and verifying that the bug exists:

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

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

root@groovy-desktop:~# apt policy sssd
sssd:
  Installed: 2.3.1-3ubuntu2
  Candidate: 2.3.1-3ubuntu2
  Version table:
 *** 2.3.1-3ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     2.3.1-3 500
        500 http://ca.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

root@groovy-desktop:~# journalctl -u sssd.service --boot 0
-- Logs begin at Wed 2020-12-09 18:34:32 EST, end at Fri 2021-01-15 13:28:44 EST. --
Jan 15 13:28:32 groovy-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 Groovy.