i should add, i tried changing ownership (recursively) for /etc/puppet, to both my user, and the puppet user, to no avail.
On Friday, July 6, 2012 12:35:17 PM UTC-4, catshirt wrote: > > hi all, > > just started using puppet and i think it's great. but i'm having a number > of problems surrounding the authentication of the servers. > > on a fresh master, when i create a new client using the node_aws cloud > provisioner (using --certname), the agent doesn't respect the generated > configuration. `certname` is certainly listed under [main] in puppet.conf, > so why wouldn't the agent recognize it? > > $ sudo puppet master --configprint certname > analytics0 > $ puppet master --configprint certname > analytics0 > $ sudo puppet agent --configprint certname > analytics0 > $ puppet agent --configprint certname > domu-x-x-x-x-x-x.compute-1.internal > $ ls -la /etc/puppet/puppet.conf > -rw-r--r-- 1 root root puppet.conf > > this pattern also occurs with the `server` option. i've also other, > unrelated but similar sudo discrepancies that i think are leading to other > problems (for another post...). for instance: > > $ sudo puppet agent --configprint ssldir > /var/lib/puppet/ssl > $ puppet agent --configprint ssldir > /home/ubuntu/.puppet/ssl > > thanks kindly! > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/RvmqFDQL0_AJ. 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-users?hl=en.
