Issue #4867 has been updated by Markus Roberts.
So it appears (empirically) that bad attribute values (e.g. a file with a mode of "foo" or a recurselimit of "bar", a notify with a withpath of 7,...) terminated the run under 0.25.x for everything I tried *except* for file owner, which used to fail the resource but not the run. With 2.6.x, they all behave the same, terminating the run rather than just failing the resource. That might be a considered a bug, but it's beyond the scope of this ticket and by our groundrules out of scope for 2.6.x. ---------------------------------------- Bug #4867: Puppet raises error when trying to set owner to non-existant user https://projects.puppetlabs.com/issues/4867 Author: Brian Gallew Status: Needs more information 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.
