Actions
Bug #3222
closedDisabling UUID certificates leaves UUID certname in place on newly created hosts
Description
Expected:
Enable use_uuid_for_certificates
Create a host
Host has a UUID now
Set host to Build, pull the host's template, watch the certname UUID value be added to the Puppet Autosign file.
... realize that uuid certificates aren't right for your organization ...
Disable use_uuid_for_certificates
Set host to Build, pull the host's template, watch the certname hostname value be added to the autosign file.
Actual:
Set host to Build, pull the host's template, watch the certname UUID value be added to the Puppet Autosign file.
Watch as your Puppet run fails to get a certificate because the client has submitted a certificate request using its hostname now.
Updated by Dominic Cleal almost 11 years ago
- Related to Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final added
Updated by Dominic Cleal almost 11 years ago
- Related to Feature #3223: Warn the user of impact of disabling UUID certificates added
Updated by Anonymous almost 11 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset 89e506f7d955b4b440725fb5ef412fb2634cd762.
Updated by Lukas Zapletal almost 11 years ago
- Related to deleted (Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final)
Updated by Dominic Cleal almost 11 years ago
- Related to Bug #3541: ec2 provisioning failure in setSSHProvision (when no CA available?) added
Updated by Dominic Cleal about 10 years ago
- Related to Bug #6566: renaming a node does not change the certname added
Actions