Sponsored for 'Eoan'. Let's start the SRU once cups land in eoan-
releases (Fix Released).
Thanks Victor !
- Eric
** Changed in: cups (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: cups (Ubuntu Disco)
Status: New => In Progress
** Changed in: cups (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: cups (Ubuntu Bionic)
Status: New => In Progress
** Changed in: cups (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot between cups and sssd
Status in cups package in Ubuntu:
Fix Committed
Status in cups source package in Xenial:
In Progress
Status in cups source package in Bionic:
In Progress
Status in cups source package in Cosmic:
In Progress
Status in cups source package in Disco:
In Progress
Status in cups source package in Eoan:
Fix Committed
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 "[email protected]"
* Set SystemGroup to match that group in /etc/cups/cups-files.conf:
SystemGroup [email protected]
* Reboot
* If cups has started before sssd has finished booting, cups will crash:
Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup
"[email protected]" 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 [email protected] 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
"[email protected]" 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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
