Issue #4867 has been updated by Nigel Kersten.
Keith Minkler wrote: > This issue is also occurring for me. The catalog is used to setup central > LDAP authentication as well as trying to set the ownership for some files to > users who are valid in LDAP. > > Before the central authentication is configured, puppet refuses to > compile/run the catalog due to missing users (who are not missing in LDAP). So to be clear, the catalog compiles, but as soon as you go to apply it, you can't, because you're referring to users who don't exist yet, even though you've set all these resources to require a class that will set up LDAP? ---------------------------------------- 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.
