Issue #4867 has been updated by Markus Roberts.
Nigel -- I don't think he's misinterpreting my comment. There are three things going on here (in order of increasing generality): 1) some resources in some manifests at some sites depend on the puppet user existing without requiring it, 2) this problem was falling through the normal checks in earlier versions of puppet, and not getting noticed, 3) the way we deal with parameter value failures is in general too abrupt and not particularly helpful. The behaviour change (2) was a bug fix and it revealed cases of (1) -- which are being fixed locally, with reported success -- but we still ought to do something about the way we respond to such errors: "Ack! Phbbth: here's a cryptic message" isn't the most useful way to respond. ---------------------------------------- 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.
