[Bug 1822062] [NEW] Race condition on boot between cups and sssd

Launchpad Bug Tracker 1822062 at bugs.launchpad.net
Wed Apr 24 16:22:19 UTC 2019


You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[Impact]

 * When cups has set the "SystemGroup" directive to an external group
provided through sss and cups starts before sssd has finished booting,
cups will crash because the group does not exist.

 * The patch adds an "After=sssd.service" clause to the service unit
file.

[Test Case]

 * Configure an external authentication service (LDAP, AD...) and create
a group, for instance "lpadmins at tests.local"

 * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
SystemGroup lpadmins at tests.local

 * Reboot

 * If cups has started before sssd has finished booting, cups will crash:
Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins at tests.local" on line 19 of /etc/cups/cups-files.conf.

 * If cups starts after sssd, it will work fine.

[Regression Potential]

 * Minimal: this patch affects just the ordering of the service unit
file.

[Other Info]

 * Upstream:
https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

[Original description]

When cups has set the "SystemGroup" directive to an external group
provided through sss and cups starts before sssd has finished booting,
cups will crash because the group does not exist. For instance, with a
group named lpadmins at tests.local served from Active Directory through
sssd, if the sssd service hasn't booted before cups:

Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers available locally.
Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins at tests.local" on line 19 of /etc/cups/cups-files.conf.
Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read "/etc/cups/cups-files.conf" due to errors.
Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 'exit-code'.
Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time over, scheduling restart.
Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, restart counter is at 2.
Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers available locally...
Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers available locally.
Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

If sssd is running before cups starts, everything works as expected.

** Affects: cups (Ubuntu)
     Importance: Medium
     Assignee: Victor Tapia (vtapia)
         Status: In Progress

** Affects: cups (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: cups (Ubuntu Bionic)
     Importance: Undecided
         Status: New

** Affects: cups (Ubuntu Cosmic)
     Importance: Undecided
         Status: New

** Affects: cups (Ubuntu Disco)
     Importance: Undecided
         Status: New

** Affects: cups (Ubuntu Eoan)
     Importance: Medium
     Assignee: Victor Tapia (vtapia)
         Status: In Progress


** Tags: patch sts
-- 
Race condition on boot between cups and sssd
https://bugs.launchpad.net/bugs/1822062
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list