Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1441860 - CUPS may fail to start if NIS groups are used
CUPS may fail to start if NIS groups are used
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cups (Show other bugs)
7.3
All Linux
medium Severity medium
: rc
: ---
Assigned To: Zdenek Dohnal
Petr Sklenar
: Patch
Depends On:
Blocks: 1420851 1465887 1465928 1494558
  Show dependency treegraph
 
Reported: 2017-04-12 18:44 EDT by Bryan Mason
Modified: 2018-04-10 09:42 EDT (History)
2 users (show)

See Also:
Fixed In Version: cups-1.6.3-30.el7
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
: 1494558 (view as bug list)
Environment:
Last Closed: 2018-04-10 09:41:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3000861 None None None 2017-04-12 18:45 EDT
Red Hat Product Errata RHBA-2018:0782 None None None 2018-04-10 09:42 EDT

  None (edit)
Description Bryan Mason 2017-04-12 18:44:00 EDT
Description of problem:

  If we place an NIS group name in the SystemGroup parameter in
  /etc/cups/cups-files.conf then CUPS will not start correctly at boot
  time and gives an error message saying there's a bad group.

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

  cups-1.6.3-26.el7.x86_64

How reproducible:

  100%

Steps to Reproduce:

 1. Add "SystemGroup <group>" to cups-files.conf, where <group> is some
    group defined in NIS.

2. Start CUPS

Actual results:

  CUPS doesn't recognize the group name.

Expected results:

  CUPS should resolve the group name.

Additional info:

  Adding "ypbind.service" to the "After=" line in the cups.service file
  appears to resolve this issue.
Comment 16 errata-xmlrpc 2018-04-10 09:41:08 EDT
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, 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/RHBA-2018:0782

Note You need to log in before you can comment on or make changes to this bug.