I hit the exact same issue, thanks for confirming this. Basically one
run (other than cert request run) in kickstart is not possible for
puppet to completely configure a node in LDAP environment.
On 3/10/11, Daniel Pittman wrote:
> Actually, it is worse than that: it is "libc, as used by Ruby, as
Actually, it is worse than that: it is "libc, as used by Ruby, as used
by Puppet"; we are several layers abstracted from the NSS data source,
and if that doesn't dynamically update we are totally stuck. Which I
understand to be the root cause here.
Regards,
Daniel
On Tue, Mar 8, 2011 at 12:4
If you are changing how the system sees users (eg before the run, 'id user'
would fail) then the "some provider" is puppet.
The workaround is to do two runs - a bootstrap base environment that sets up
ldap, then a second run that uses those users.
On Thu, Feb 17, 2011 at 6:50 AM, Felix Frank <
fe
On 02/15/2011 11:49 PM, Jay N. wrote:
> Hi Puppet Users,
>
> In my configuration, I modify in the "pre" stage the ldap.conf file
> which is originally generic and useless.
>
> Then, in the main stage, I try to modify the ownership of files with
> ldap users and groups and I have an error "Cannot
