Re: Node names as IPs not hostnames

2018-10-09 Thread Dan Pungă
Hi Rich! What I understand from the description of your github issue is that you're trying to achieve node names as their IP addresses when specifically integrating with OpenStack. My problem is that I don't want to integrate with OpenStack, but the openshift_facts.py script from the 3.9

Re: Node names as IPs not hostnames

2018-10-09 Thread Rich Megginson
Are you hitting https://github.com/openshift/openshift-ansible/pull/9598 ? On 10/9/18 11:25 AM, Dan Pungă wrote: Thanks for the reply Scott! I've used the release branches for both 3.9 and 3.10 of the openshift-ansible project, yes. I've initially checked the openshift_facts.py script flow in

Re: Node names as IPs not hostnames

2018-10-09 Thread Dan Pungă
Thanks for the reply Scott! I've used the release branches for both 3.9 and 3.10 of the openshift-ansible project, yes. I've initially checked the openshift_facts.py script flow in the 3.9 branch; now looking at the 3.10 version, I do see the change that you're pointing. On 09.10.2018

Re: Node names as IPs not hostnames

2018-10-08 Thread Dan Pungă
I've done a bit of digging and apparently my problem is precisely connected to the fact that I'm running the cluster on the OpenStack provider. Briefly put, the openshift_facts playbook relies on the openshift-ansible/roles/openshift_facts/library/openshift_facts.py script. This script uses

Node names as IPs not hostnames

2018-10-08 Thread Dan Pungă
Hello all, I'm trying to upgrade a working cluster from Openshift Origin 3.9 to OKD 3.10 and the control plane update fails at one point with host not found. I've looked abit over the problem and found this issue on github: https://github.com/openshift/openshift-ansible/issues/9935 where