Project

General

Profile

Actions

Bug #35679

open

autosign.conf gets FQDN when "Append domain names to the host" is no and a host is rebuilt

Added by Robert Eden over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
easy
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

When Foreman setting "Append domain names to the host" is set to no:

puppet.conf "certname" has the shortname
autosign.conf has the FQDN

They probably should both have the shortname, but they certainly should match!

Foreman 2.5.4-1

Actions #1

Updated by Robert Eden over 1 year ago

stand by... I think the issue only occurs when the host is edited. I deleted and recreated and it autosign had a short-name. Let me confirm the steps to duplicate.

Actions #2

Updated by Robert Eden over 1 year ago

  • Subject changed from certname doesn't match autosign.conf when "Append domain names to the host" is no to autosign.conf gets FQDN when "Append domain names to the host" is no and a host is rebuilt

puppet.conf certname has short name (as it should)

the problem is with autosign.conf

steps to reproduce
1. create host (autosign has short name)
2. cancel build (autosign removes short name)
3. initiate build (autosign gets FQDN BUG)
4. cancel build (autosign still has FQDN... (it will remove short_name if you put it back after step 3!))

Actions #3

Updated by Robert Eden over 1 year ago

I noticed when the rebuild host boots, it shows up as a new host (host list has 2 with the same short-name).. so maybe the issue is with the "cancel"/"build" process and the puppet side is only a symptom. I don't know enough about foreman internals to tell.

Actions

Also available in: Atom PDF