I have a situation where some of my puppet client machines fqdn's change. After this happens they fail to connect to the puppet master due to an untrusted certificate. It looks like manually setting a "certname" in the client puppet.conf file will work around this issue of the certname relying on the fqdn of the machine. Is this correct? Are there any gotcha's that I should be aware of before setting the certname setting in the client puppet.conf?
(I realize I'll have to resign and certs where the newly set certname is different than the current certname.) Thanks, -- Romeo -- 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.
