Issue #4867 has been updated by Brian Gallew. File no_puppet_user_group.log added
I installed both facter and puppet with the follwing: `chroot /a /bin/bash -c "HOME=/;export HOME;cd /var/tmp;PATH=$PATH:/opt/webstack/bin;gem install --no-rdoc --no-ri facter" chroot /a /bin/bash -c "HOME=/;export HOME;cd /var/tmp;PATH=$PATH:/opt/webstack/bin;gem install --no-rdoc --no-ri puppet"` FTR, that's cut-and-pasted from a Solaris Jumpstart finish script. I've attached a lot of running puppet on a Solaris system with neither the puppet user nor the puppet group. In my case I can trivially reproduce the problem just by doing the relevant userdel/groupdel. ---------------------------------------- Bug #4867: On Solaris, puppet client requires the puppet user to exist before running http://projects.puppetlabs.com/issues/4867 Author: Brian Gallew Status: Needs more information Priority: Normal Assignee: Nick Lewis Category: agent Target version: 2.6.x Affected version: 2.6.1 Keywords: Branch: WHen I ran 0.25.5, I relied on the puppet client to create the puppet user. Since I've upgraded to 2.6.1, the puppet user must already exist before the puppet client will run, otherwise the puppet client bails with an error: err: Could not run Puppet configuration client: Could not find user puppet This seems to be a fairly major regression. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
