Bug 1329496

Summary:	The parameter 'osm_default_subdomain' didn't take effect
Product:	OpenShift Container Platform	Reporter:	Ma xiaoqiang <xiama>
Component:	Installer	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED ERRATA	QA Contact:	Ma xiaoqiang <xiama>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	aos-bugs, jokerman, mmccomas, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-07 10:55:20 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 Ma xiaoqiang 2016-04-22 06:09:26 UTC

Description of problem:
The parameter 'osm_default_subdomain' didn't take effect


Version-Release number of selected component (if applicable):
openshift-ansible-3.0.83-1


How reproducible:
always

Steps to Reproduce:
1. install  env 
vim hosts
<--snip-->
osm_default_subdomain="test.example.com"
<--snip-->
$ ansible-playbook -i hosts openshift-ansible/playbooks/byo/config.yaml -v

2. check the master config

Actual results:
<--snip-->
routingConfig:
  subdomain:  ""
serviceAccountConfig:
<--snip-->

The value of subdomain is wrong

Expected results:
The parameter 'osm_default_subdomain' should take effect

Additional info:

Comment 1 Jason DeTiberus 2016-04-22 19:02:15 UTC

Working on addressing this here: https://github.com/openshift/openshift-ansible/pull/1793

Comment 3 Ma xiaoqiang 2016-05-25 01:03:28 UTC

Check on openshift-ansible-3.0.93-1

Install environment with the following options
<--snip-->
openshift_master_default_subdomain_enable=true
osm_default_subdomain=0525-m08.qe.rhcloud.com
<--snip-->

check the master configuration.
routingConfig:
  subdomain:  "0525-m08.qe.rhcloud.com"
<--snip-->

Get the expected result, move it to VERIFIED.

Comment 5 errata-xmlrpc 2016-06-07 10:55:20 UTC

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-2016:1208