Previously we had to set the system hostname to workaround unconfigurable code paths that would use uname to lookup the system's hostname. This should no longer be necessary as we can override all of the necessary hostnames using configuration.
https://github.com/openshift/openshift-ansible/pull/924
We need to make sure that this change doesn't break OSE 3.0.0 deployments as well.
If the system hostname is not resolved, we can get the error messages in the log Nov 19 15:26:52 openshift-v3 atomic-openshift-master: E1119 15:26:52.466917 28396 common.go:722] Failed to lookup IP address for node test2.redhat.com: lookup test2.redhat.com: no such host Nov 19 15:26:52 openshift-v3 atomic-openshift-master: F1119 15:26:52.466973 28396 flatsdn.go:27] SDN initialization failed: lookup test2.redhat.com: no such host Is it worse to set the system hostname?
Can you provide the following files from the system that threw that error? - /etc/origin/node/node-config.yaml - /etc/ansible/facts.d/openshift.fact - ansible inventory file
This is breaking QE's auto installation, so raise its priority.
This issue is also blocking the installation of atomic-openshift-installer when setting hostname needed, since there's no way to specify the value of openshift_set_hostname during the interaction. Test with: openshift-ansible-3.0.16-1.git.61.2054960.el7aos.noarch openshift-ansible-roles-3.0.16-1.git.61.2054960.el7aos.noarch
Hi Gaoyun, When you say there is no way to set openshift_set_hostname do you mean using atomic-openshift-installer? Jason will probably chime in if I'm confused by I think you would would need to set it in your inventory: https://github.com/openshift/openshift-ansible/pull/967/files#diff-786740a46e25ab5676fd83c2bf6b4197R155
This should be testable with the latest puddle. Also, I see now that Comment #12 is indeed referring to atomic-openshift-installer. I'm removing needinfo.
To be clear, this bug is for testing the feature by running ansible directly.
Get the expected result. Move it to VERIFIED.
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/RHBA-2015:2667