Red Hat Bugzilla – Bug 1280171
Fail to install env on Atomic when 'openshift_set_hostname' is true
Last modified: 2016-07-03 20:47:18 EDT
Description of problem:
Should set hostname of atomic in playbook
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install env on atomic without setting hostname of atomic
Can not start master service
Nov 11 12:59:11 atomic.nay.redhat.com docker: E1110 23:59:11.528140 1 common.go:722] Failed to lookup IP address for node atomic.nay.redhat.co...such host
Nov 11 12:59:11 atomic.nay.redhat.com docker: F1110 23:59:11.528178 1 flatsdn.go:27] SDN initialization failed: lookup atomic.nay.redhat.com: no such host
Start the master service successfully
The playbook will configure hostname of rhel. we also can configure the hostname of atomic via shell or command.
I've submitted https://github.com/openshift/openshift-ansible/pull/924 to remove setting the hostname.
Since the hostname workaround is no longer needed, we should pull this into the containerization work as well.
The setting of hostname has been removed from ansible. I'd say that the SDN requires the nodename be resolvable at this point in time. This isn't a containerization specific issue.
If we do not set hostname. we can not start the master service. The setting of hostname has been removed from ansible, so the master still can not be restarted.
Even if the ansible set the hostname, the module 'hostname' in ansible still doesn't support atomic platform.
I need to check with Jason on the latest for when we need to set the hostname. I don't think that we need this functionality in the majority of cases.
After discussing this with Jason there are still major problems associated with setting a hostname that doesn't resolve and those won't be fixed until kube 1.2 or later. However if you want to set the hostname of a host to a valid hostname we should allow you to do that.
Here's my proposed fix https://github.com/openshift/openshift-ansible/pull/1165
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.