Project

General

Profile

Actions

Bug #23754

closed

Foreman 1.17 auto-installation fails with "Forward DNS 10.3.1.11 did not reverse resolve to any hostname."

Added by Tina Ryn almost 6 years ago. Updated almost 6 years ago.

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

Description

Noticed, when I tried to install version 1.17:

Forward DNS 10.3.1.11 did not reverse resolve to any hostname.
Your system does not meet configuration criteria

That's not very verbose, but the error message points towards https://github.com/Katello/katello-installer/blob/master/checks/dns.rb

This issue may be related to #22260 since I can auto-install Foreman 1.15 just fine (didn't check 1.16).


Related issues 1 (0 open1 closed)

Related to Installer - Bug #23871: dns checker returns empty string for fqdn resolting in wrong error messageRejectedIdo KannerActions
Actions #1

Updated by Tina Ryn almost 6 years ago

Noticed, when I tried to install version 1.17:

Forward DNS 10.3.1.11 did not reverse resolve to any hostname.
Your system does not meet configuration criteria

That's not very verbose, but the error message points towards https://github.com/Katello/katello-installer/blob/master/checks/dns.rb

This issue may be related to #22260 since I can auto-install Foreman 1.15 just fine (checked foreman-installer 1.16 - no error as well).

Actions #2

Updated by Tina Ryn almost 6 years ago

And adding server name and ip to /etc/hosts worked as a bypass.

Actions #3

Updated by Ondřej Pražák almost 6 years ago

  • Project changed from Foreman to Installer

Moving to installer

Actions #4

Updated by Anonymous almost 6 years ago

  • Status changed from New to Feedback

If that IP doesn't resolve correctly the check IMHO indeed did its job and the message is correct.

That check got added to avoid problems later in setups without correct forward and reverse resolving (#8301)

At the moment I don't see a reason to change anything. Tina, please let us know, if there are problems besides the check.

Actions #5

Updated by Anonymous almost 6 years ago

  • Related to Bug #23871: dns checker returns empty string for fqdn resolting in wrong error message added
Actions

Also available in: Atom PDF