Renaming a host seems to fix dns, but it leaves the old host name in provisioning templates

Support
1

Anyone know a way to fix this or should i file a bug? it seems if you
rename a managed host, it updates the host in the primary interfaces but if
you go and view the finish template, it shows the old host in there even
after saving. So if you re-provision the host, it gets the new hostname,
but puppet (or anything in finish template) seems to use the prior hostname.

2

Seems like its this code that has an old reference after renaming.

certname = <%= @host.certname %>

··· On Sunday, September 25, 2016 at 3:08:07 PM UTC-5, Byron Miller wrote: > > Anyone know a way to fix this or should i file a bug? it seems if you > rename a managed host, it updates the host in the primary interfaces but if > you go and view the finish template, it shows the old host in there even > after saving. So if you re-provision the host, it gets the new hostname, > but puppet (or anything in finish template) seems to use the prior hostname. >
3

> Seems like its this code that has an old reference after renaming.
>
> certname = <%= @host.certname %>
>
certname is not hostname, usually its a UUID (assuming the setting is on)
to avoid name conflicts within certificates…

if you are not using that feature, then you could replace it within the
template?

Ohad

··· On Sun, Sep 25, 2016 at 11:16 PM, Byron Miller wrote:

On Sunday, September 25, 2016 at 3:08:07 PM UTC-5, Byron Miller wrote:

Anyone know a way to fix this or should i file a bug? it seems if you
rename a managed host, it updates the host in the primary interfaces but if
you go and view the finish template, it shows the old host in there even
after saving. So if you re-provision the host, it gets the new hostname,
but puppet (or anything in finish template) seems to use the prior hostname.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

I must have an old setting, the certname matches hostname. I'll try
switching to UUID.

··· On Monday, September 26, 2016 at 1:40:13 AM UTC-5, ohad wrote: > > > > On Sun, Sep 25, 2016 at 11:16 PM, Byron Miller > wrote: > >> Seems like its this code that has an old reference after renaming. >> >> certname = <%= @host.certname %> >> > certname is not hostname, usually its a UUID (assuming the setting is on) > to avoid name conflicts within certificates.. > > if you are not using that feature, then you could replace it within the > template? > > Ohad > >> >> >> On Sunday, September 25, 2016 at 3:08:07 PM UTC-5, Byron Miller wrote: >>> >>> Anyone know a way to fix this or should i file a bug? it seems if you >>> rename a managed host, it updates the host in the primary interfaces but if >>> you go and view the finish template, it shows the old host in there even >>> after saving. So if you re-provision the host, it gets the new hostname, >>> but puppet (or anything in finish template) seems to use the prior hostname. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >