On Apr 14, 2011, at 11:57 AM, Jake - USPS wrote:
Thanks Matt. Just for clarification on why I'm trying to do this. We
often rebuild systems in our environment. Things are
'decommissioned', hostname 'released' and new system built with
previously used hostname for new purposes. This means
Users
Subject: [Puppet Users] Re: allow_duplicate_certs = true not working?
Thanks Matt. Just for clarification on why I'm trying to do
this. We often rebuild systems in our environment. Things
are 'decommissioned', hostname 'released' and new system
built with previously used hostname
Here is the output:
eagnmnmbpe20:/etc/puppet # puppet certificate generate `hostname` --ca-
location remote --server eagnmnmbpe26.usps.gov --masterport 9443
notice: /Whit[completed_/etc/puppet/ssl]: Triggered 'refresh' from 1
events
notice: /Whit[completed_/etc/puppet/ssl/private]: Triggered
Jake
The behavior in 2.7 when running the master with
--allow_duplicate_certs set is the same as in 2.6.x in that you can
manually (using something like curl or the new 'puppet certificate'
face) generate multiple certs with same CN name, but the agent errors
the same way regardless of the puppet
Thanks Matt. Just for clarification on why I'm trying to do this. We
often rebuild systems in our environment. Things are
'decommissioned', hostname 'released' and new system built with
previously used hostname for new purposes. This means currently (as I
understand it) part of our decom
