Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4394

Regression: Webrick fails to start if the puppet user and group don't exist

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: PUP 4.0.0
    • Fix Version/s: PUP 4.1.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      2
    • Sprint:
      Client 2015-04-29

      Description

      If you install puppet-agent and try to start webrick, it will attempt to switch to the puppet user and group, and fail, because the puppet-agent package no longer creates these accounts.

      [root@yvf37tnj11yfmn1 ~]# puppet master --verbose --no-daemonize
      Warning: could not change to group "puppet": Invalid group: puppet
      could not change to group "puppet"
      Could not change to user puppet: Invalid user: puppet
      

      The desired behavior is that puppet's webrick code should not switch uid/gid to a non-existent account.

      To work around the issue, specify the puppet user and group to accounts that are known to exist, either in puppet.conf, command line, etc:

      [root@yvf37tnj11yfmn1 ~]# puppet master --verbose --no-daemonize --user root --group root
      Notice: Starting Puppet master version 4.0.0
      

      This was not discovered earlier because we have only been testing webrick on hosts where puppetserver is installed, and that package does create the puppet user and group.

      Risk Assessment: low (but already verified)
      Probability: low (webrick)
      Impact: low (obvious problem, existing warnings/errors)
      Test Layer: Unit/Integration

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                josh Josh Cooper
                QA Contact:
                Kurt Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support