Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1346080 - Satellite installer checks that hostname is valid, but does not check if it resolves to an IP on the configured system.
Summary: Satellite installer checks that hostname is valid, but does not check if it r...
Keywords:
Status: CLOSED DUPLICATE of bug 1243566
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-13 21:43 UTC by Rich Jerrido
Modified: 2016-07-07 13:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-07 13:36:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Rich Jerrido 2016-06-13 21:43:37 UTC 
Description of problem:

When running satellite-installer, the installer checks that hostname is resolvable, but does not check if it resolves to an IP on the configured system. 


Example:

If my system is satellite.example.com and has the locally configured IP address of 172.16.0.1, but satellite.example.com resolves to some other IP (say 192.168.0.1), the installer checks pass and the installer proceeds. However, it will potentially fail, as 192.168.0.1 isnt the local system, and many of the components connect via FQDN. 



Version-Release number of selected component (if applicable):
satellite-installer-6.2.0.8-1.el7sat.noarch

How reproducible:
100

Steps to Reproduce:
1. install a system as satellite.example.com

2. create a DNS record that resolves satellite.example.com to an IP that is NOT on configured on the system which you are installing Satellite on. 

3. run the installer. 

Actual results:

Installer proceeds & fails with error (due to one of the services having name resolution issues). 

Expected results:


Installer should halt and inform the user that the hostname does not resolve to a locally configured IP.
Comment 3 Rich Jerrido 2016-06-26 19:33:38 UTC 
Changing title to more clearly reflect the nature of this BZ. Installer checks that the hostname is valid. (ie. it ensures hostname.domain.com), but it doesnt ensure that

- hostname is resolvable (either via the configured resolver or via /etc/hosts)
- the resolved hostname's IP is one that is locally configured on the system you are running satellite-installer on.
Comment 4 Chris Roberts 2016-07-07 13:36:43 UTC 

*** This bug has been marked as a duplicate of bug 1243566 ***
Note You need to log in before you can comment on or make changes to this bug.