Bug 1277712

Summary:	unattended installation results in using ips instead of hostnames
Product:	OpenShift Container Platform	Reporter:	Erik M Jacobs <ejacobs>
Component:	Installer	Assignee:	Samuel Munilla <smunilla>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ma xiaoqiang <xiama>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	aos-bugs, bleanhar, dmcphers, gpei, jokerman, mmccomas, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift-ansible-3.0.7-1.git.87.c20c024.el7aos	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-20 15:42:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Erik M Jacobs 2015-11-03 21:55:37 UTC

atomic-openshift-utils 3.0.6-1.git.1.e0fd136.el7aos

Using the following YAML configuration file and running the installer unattended, the installer ends up using the ip addresses instead of the hostnames.

If you use the installer interactively then it correctly uses the hostnames:

ansible_log_path: /tmp/ansible.log
ansible_ssh_user: root
hosts:
- hostname: ose3-master.example.com
  ip: 192.168.133.2
  master: true
  node: true
  public_hostname: ose3-master.example.com
  public_ip: 192.168.133.2
- hostname: ose3-node1.example.com
  ip: 192.168.133.3
  node: true
  public_hostname: ose3-node1.example.com
  public_ip: 192.168.133.3
- hostname: ose3-node2.example.com
  ip: 192.168.133.4
  node: true
  public_hostname: ose3-node2.example.com
  public_ip: 192.168.133.4
variant: openshift-enterprise
variant_version: '3.1'

Comment 2 Brenton Leanhardt 2015-11-06 19:19:57 UTC

This should be fixed in the next puddle.