group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #30263
[Bug 1822062] Re: Race condition on boot between cups and sssd
This bug was fixed in the package cups - 2.2.7-1ubuntu2.5
---------------
cups (2.2.7-1ubuntu2.5) bionic; urgency=medium
* d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)
-- Victor Tapia <victor.tapia@xxxxxxxxxxxxx> Wed, 24 Apr 2019 16:58:30
+0200
** Changed in: cups (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot between cups and sssd
Status in cups package in Ubuntu:
Fix Released
Status in cups source package in Xenial:
Fix Released
Status in cups source package in Bionic:
Fix Released
Status in cups source package in Cosmic:
Fix Released
Status in cups source package in Disco:
Fix Released
Status in cups source package in Eoan:
Fix Released
Bug description:
[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@tests.local"
* Set SystemGroup to match that group in /etc/cups/cups-files.conf:
SystemGroup lpadmins@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@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@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@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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+subscriptions