Description of problem: Installer get stuck at "Gathering information from hosts..." if bad hostname checked Version-Release number of selected component (if applicable): atomic-openshift-utils-3.5.8-1.git.0.0e02ef8.el7 How reproducible: always Steps to Reproduce: 1.prepare a host for installation # hostname openshift-129.lab.eng.nay.redhat.com # getent ahostsv4 `hostname` | head -n 1 | awk '{ print $1 }' 10.66.147.129 # ip a show dev eth0 ... inet 192.168.2.140/24 brd 192.168.2.255 scope global dynamic eth0 ... 2.atomic-openshift-installer install 3. Actual results: # atomic-openshift-installer install ... Gathering information from hosts... Installer stuck here Expected results: Installation succeed Additional info: # tailf /tmp/ansible.log ... 2017-02-15 18:24:01,036 p=21540 u=root | TASK [Warn user about bad openshift_hostname values] *************************** 2017-02-15 18:24:01,102 p=21540 u=root | [Warn user about bad openshift_hostname values] The hostname "openshift-129.lab.eng.nay.redhat.com" for "openshift-129.lab.eng.nay.redhat.com" doesn't resolve to an ip address owned by this host. Please set openshift_hostname variable to a hostname that when resolved on the host in question resolves to an IP address matching an interface on this host. This host will fail liveness checks for pods utilizing hostPorts, press ENTER to continue or CTRL-C to abort.:
If anything clarify the warning message, but essentially we're halting a bad install and advising them that they should use an internal hostname.
(In reply to Scott Dodson from comment #1) > If anything clarify the warning message, but essentially we're halting a bad > install and advising them that they should use an internal hostname. Can get a warning message to guide user continue install in 3.4/3.3/3.2, wish the code could merge to 3.5.
Are you saying this is a regression? I'd expect this to behave the same way in 3.4/3.3/3.2. If this is a regression then this is a blocker. Can you provide the contents of /etc/hosts from a host you're seeing this on in addition to all of the information already provided (encase you reproduce this on a new host it may change)?
https://github.com/openshift/openshift-ansible/pull/3853
I think it's a simple issue, do you think we can fix it in 3.5? \ There is a PR in comment #5
This seems like a reasonable fix to me. I'm going to pass this to Tim so that he can review and ship it when he has time.
Verified with version atomic-openshift-utils-3.5.66-1.git.0.cfa474b.el7, never get stuck at "Gathering information from hosts..." when bad hostname checked.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1244