Project

General

Profile

Actions

Bug #2357

open

inconsistent handling of FQDN with trailing dot

Added by Darrell Budic about 11 years ago. Updated about 11 years ago.

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

Description

Foreman appears to handle FQDNs with a trailing dot inconstantly in it's validation, leading to at least two problems, one major (unable to login on new installation):
1) When the admin account is created on a host with a trailing dot in dns, the email address gets set to . . The trailing dot causes the password setting (or a rake permissions:reset) to fail with "Mail is invalid". Editing the db to change the email address to one without a trailing dot allows things to work properly.
2) Foreman and foreman-proxy setup their reference to the host's ssl certificate differently. In my case, foreman had "fqdn.com.pem", and foreman-proxy had "fqdn.com..pem". The certificates & keys were actually created as "fqdn.com..pem". I moved them to "fqdn.com.pem" and updated foreman-proxy's settings appropriately to resolve the problem.

Actions #1

Updated by Darrell Budic about 11 years ago

Oh, the fqdn trailing dot came from reverse-dns PTR records, the hostname was set without it, so foreman picked this up from the rdns I think.

Actions

Also available in: Atom PDF