Are you specifying certname on puppet master as well as client? That is working for me as long as I set --server=<master_certname> and --certname=<client_certname> on the client and --certname=<master_certname> on the master. You may need to clean out <confdir>/ssl on your AMIs and start over to get this to work.
Specifying certname enables using puppet in EC2 with dynamic DNS. Then master and clients can be stopped and started and still authenticate without updating certs, even though public DNS name and IP address usually change between AMI start & stop. It would be nice to expose the node name in puppet master notice statements for debugging, but I haven't found a way to do that. This is not the same as hostname, nor is it what you get from internal reverse DNS in EC2, nor is it the same as name, which seems to be derived from whatever regex matched the node declaration. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
