Comment 17 for bug 1822062

# VERIFICATION: BIONIC
- Using the reproducer defined in the test case and the version in -updates:

ubuntu@bionic-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.7-1ubuntu2.4 amd64 Common UNIX Printing System(tm) - PPD/driver support, web interface
ii cups-common 2.2.7-1ubuntu2.4 all Common UNIX Printing System(tm) - common files
ii cups-daemon 2.2.7-1ubuntu2.4 amd64 Common UNIX Printing System(tm) - daemon

ubuntu@bionic-sssd-ad:~$ grep -i systemgroup /etc/cups/cups-files.conf
SystemGroup <email address hidden>

ubuntu@bionic-sssd-ad:~$ systemd-analyze critical-chain cups.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

cups.service @5d 44min 17.034s
└─basic.target @41.538s
  └─sockets.target @41.534s
    └─lxd.socket @41.422s +104ms
      └─sysinit.target @41.320s
        └─systemd-update-utmp.service @40.757s +99ms
          └─systemd-tmpfiles-setup.service @39.550s +1.181s
            └─local-fs.target @13.659s
              └─var-lib-lxcfs.mount @43.131s
                └─local-fs-pre.target @9.991s
                  └─systemd-tmpfiles-setup-dev.service @8.859s +1.127s
                    └─kmod-static-nodes.service @8.510s +303ms
                      └─systemd-journald.socket @8.460s
                        └─system.slice @8.334s
                          └─-.slice @8.326s

- After reboot, cups fails to start:

ubuntu@bionic-sssd-ad:~$ systemctl status cups
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-05-07 10:06:32 UTC; 27min ago
     Docs: man:cupsd(8)
  Process: 969 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
 Main PID: 969 (code=exited, status=1/FAILURE)

May 07 10:06:32 bionic-sssd-ad systemd[1]: cups.service: Service hold-off time over, scheduling restart.
May 07 10:06:32 bionic-sssd-ad systemd[1]: cups.service: Scheduled restart job, restart counter is at 5.
May 07 10:06:32 bionic-sssd-ad systemd[1]: Stopped CUPS Scheduler.
May 07 10:06:32 bionic-sssd-ad systemd[1]: cups.service: Start request repeated too quickly.
May 07 10:06:32 bionic-sssd-ad systemd[1]: cups.service: Failed with result 'exit-code'.
May 07 10:06:32 bionic-sssd-ad systemd[1]: Failed to start CUPS Scheduler.

ubuntu@bionic-sssd-ad:~$ grep cupsd /var/log/syslog | grep -v kernel
May 7 10:06:30 bionic-sssd-ad cupsd[860]: Unknown SystemGroup "<email address hidden>" on line 19 of /etc/cups/cups-files.conf.
May 7 10:06:30 bionic-sssd-ad cupsd[860]: Unable to read "/etc/cups/cups-files.conf" due to errors.
...

- Using the version in -proposed, after rebooting, cups works fine:

ubuntu@bionic-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.7-1ubuntu2.5 amd64 Common UNIX Printing System(tm) - PPD/driver support, web interface
ii cups-common 2.2.7-1ubuntu2.5 all Common UNIX Printing System(tm) - common files
ii cups-daemon 2.2.7-1ubuntu2.5 amd64 Common UNIX Printing System(tm) - daemon

ubuntu@bionic-sssd-ad:~$ systemctl status cups
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-05-07 10:36:49 UTC; 9min ago
     Docs: man:cupsd(8)
 Main PID: 1036 (cupsd)
    Tasks: 1 (limit: 2361)
   CGroup: /system.slice/cups.service
           └─1036 /usr/sbin/cupsd -l

May 07 10:36:49 bionic-sssd-ad systemd[1]: Started CUPS Scheduler.
ubuntu@bionic-sssd-ad:~$ systemd-analyze critical-chain cups.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

cups.service @46.601s
└─sssd.service @39.137s +7.411s
  └─basic.target @39.068s
    └─sockets.target @39.062s
      └─snapd.socket @38.991s +62ms
        └─sysinit.target @38.817s
          └─cloud-init.service @35.077s +3.695s
            └─systemd-networkd-wait-online.service @33.910s +1.151s
              └─systemd-networkd.service @33.667s +205ms
                └─network-pre.target @33.654s
                  └─cloud-init-local.service @19.639s +14.007s
                    └─systemd-remount-fs.service @6.538s +851ms
                      └─systemd-journald.socket @6.460s
                        └─system.slice @6.408s
                          └─-.slice @6.129s

- Using the version in -proposed, with sssd not installed in the machine (and setting SystemGroup to the original local group "lpadmin"), cups still starts:

ubuntu@bionic-sssd-ad:~$ systemctl status cups
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-05-07 10:49:34 UTC; 2min 24s ago
     Docs: man:cupsd(8)
 Main PID: 895 (cupsd)
    Tasks: 1 (limit: 2361)
   CGroup: /system.slice/cups.service
           └─895 /usr/sbin/cupsd -l

May 07 10:49:34 bionic-sssd-ad systemd[1]: Started CUPS Scheduler.
ubuntu@bionic-sssd-ad:~$ systemd-analyze critical-chain cups.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

cups.service @28.727s
└─basic.target @27.107s
  └─sockets.target @27.100s
    └─snapd.socket @26.970s +103ms
      └─sysinit.target @26.621s
        └─cloud-init.service @24.766s +1.849s
          └─systemd-networkd-wait-online.service @23.481s +1.264s
            └─systemd-networkd.service @23.306s +153ms
              └─network-pre.target @23.300s
                └─cloud-init-local.service @15.552s +7.742s
                  └─systemd-remount-fs.service @3.434s +198ms
                    └─systemd-journald.socket @3.385s
                      └─system.slice @3.337s
                        └─-.slice @3.160s