RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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