Bug 1938384

Summary:	CUPS doesn't start if sssd starts after cupsd
Product:	Red Hat Enterprise Linux 8	Reporter:	Bryan Mason <bmason>
Component:	cups	Assignee:	Zdenek Dohnal <zdohnal>
Status:	CLOSED ERRATA	QA Contact:	Petr Dancak <pdancak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	pdancak, psklenar
Target Milestone:	rc	Keywords:	Patch, TestCaseProvided, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cups-2.2.6-39.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1949053 (view as bug list)		Environment:
Last Closed:	2021-11-09 19:38:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1949053

Description Bryan Mason 2021-03-13 01:46:00 UTC

Description of problem:

  CUPS sometimes fails to start when sssd is used to resolve user/group
  names.

Version-Release number of selected component (if applicable):

  cups-2.2.6-38.el8.x86_64

How reproducible:

  Unknown

Steps to Reproduce:

1. start cups

Actual results:

  If sssd starts before cupsd, all is good.
  if cupsd starts before sssd, cupsd fails to start.

Expected results:

  cupsd should always start

Additional info:

  This is effectively the same issue raised in Bug 1441860
  but with sssd instead of ypbind.

  sssd.service is included in the "After=" line in
  scheduler/cups.service.in upstream, however I think it makes more
  sense to use the nss-user-lookup.target in the "After=" line rather
  than just adding every possible service that could be used to resolve
  user names.

  I've filed a pull request upstream to use nss-user-lookup.target instead
  of all the .service units:

    https://github.com/OpenPrinting/cups/pull/141

Comment 17 errata-xmlrpc 2021-11-09 19:38:31 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: cups security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4393