Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Done
-
PUP 4.0.0
-
None
-
None
-
2
-
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
- relates to
-
PUP-4441 Create test to show that Webrick doesn't start if the "puppet" user and group do not exist
-
- Closed
-
-
PUP-4435 Deprecate Puppet WEBrick and Rack servers
-
- Closed
-
-
PUP-4317 Smoke test packages
-
- Resolved
-
-
PUP-5317 Master should return 74 when puppet user doesn't exist
-
- Closed
-
-
PUP-4453 too many warnings/errors when master can't start due to no puppet user/group
-
- Closed
-
- links to