Project

General

Profile

Actions

Bug #6566

closed

renaming a node does not change the certname

Added by David Schmitt almost 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet integration
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #3222: Disabling UUID certificates leaves UUID certname in place on newly created hostsClosed10/08/2013Actions
Actions

Also available in: Atom PDF