Issue #4867 has been updated by Nigel Kersten.
Note too that if you *know* the uid of your remote users, you can refer to them
by uid, and Puppet will simply set the owner/group to the numeric value and no
name validation is done at all.
<pre>
file { "/tmp/bar":
ensure => present,
owner => 666,
}
</pre>
<pre>
-rw-r--r-- 1 666 root 0 2011-03-10 13:49 /tmp/bar
</pre>
This may be a good workaround for some of you.
----------------------------------------
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.
