Bug #6566
closed
renaming a node does not change the certname
Added by David Schmitt over 10 years ago.
Updated over 6 years ago.
Category:
Puppet integration
|
Description
Reproduction:
1. Create a new host with the name 'test.example.com'
2. Render a provisioning template containing @host.certname. Output should contain 'test.example.com'
3. provision the host (I've not checked this step, but solely creating the host does not seem enough to repro this)
3. Edit the host and change the hostname to 'different.example.com'
4. Render a provisioning template containing @host.certname.
Expected output 'different.example.com'
Actual output 'test.example.com'
My specific use-case is renaming kickstartable hosts. When the certname does not change together with the hostname, this causes massive havok when trying to rebuild hosts.
- Category set to Puppet integration
Related to #3222. Instead of zapping the certificate only if we've changed from uuid to named certificates, what if we always zap the certificate when we're in hostname mode? This will handle both the case described in #3222 (changing from uuid to hostname) and also when renaming a machine with hostname certnames.
- Pull request https://github.com/theforeman/foreman/pull/1604 added
- Pull request deleted (
)
- Status changed from New to Ready For Testing
- Target version set to 1.8.0
- Assignee set to Aaron Stone
- Translation missing: en.field_release set to 10
- Target version changed from 1.8.0 to 1.7.5
- Related to Bug #3222: Disabling UUID certificates leaves UUID certname in place on newly created hosts added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF