Issue #4867 has been updated by Nigel Kersten. Status changed from Rejected to Investigating Assignee changed from Markus Roberts to Nigel Kersten Target version changed from 2.6.3 to 2.6.x
Brian, is that really how it behaved before? I've always been under the impression puppet didn't make the puppet user and group on the client automatically, but if we have had a significant behavior change, we should be certainly calling it out in real documentation and/or remediating the issue. Do you think Markus has mis-characterized the issue here? I think you may have misinterpreted his comment in https://projects.puppetlabs.com/issues/4867#note-27 as he is definitely talking about a wider issue. If we need to address the wider issue, then we can do so. ---------------------------------------- Bug #4867: Puppet raises error when trying to set owner to non-existant user https://projects.puppetlabs.com/issues/4867 Author: Brian Gallew Status: Investigating Priority: Normal Assignee: Nigel Kersten Category: agent Target version: 2.6.x Affected Puppet version: 2.6.1 Keywords: Branch: http://github.com/MarkusQ/puppet/tree/ticket/2.6.x/4867 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.
