Issue #4867 has been updated by Brian Gallew.
Just so that I am clear on the resolution here: 1) Puppet failing to run *at all* in the case where a required user is unavailable is the new "correct" behavior for 2.6.x in spite of the fact that if puppet were to run the user would be created (because that's how it always worked before). 2) The new behavior will be documented by this ticket (only) 3) Tickets which are declared "out of scope" are simply rejected instead of being pointed to an appropriate version. ---------------------------------------- Bug #4867: Puppet raises error when trying to set owner to non-existant user https://projects.puppetlabs.com/issues/4867 Author: Brian Gallew Status: Rejected Priority: Normal Assignee: Markus Roberts Category: agent Target version: 2.6.3 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.
