Red Hat Bugzilla – Bug 1308313
osm_default_subdomain would be removed from ansible inventory when run atomic-openshift-installer unattended
Last modified: 2016-02-29 07:57:54 EST
Description of problem:
atomic-openshift-installer is allowed to define default subdomain now, but once user choose editing the installer.cfg.yml during interaction and run `atomic-openshift-installer --unattended install` to restart the install, osm_default_subdomain was removed from ansible inventory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run 'atomic-openshift-installer install'
2.Input the required information including subdomain name
3.Choose "N" for the facts confirm, edit the installer.cfg.yml and run 'atomic-openshift-installer --unattended install'
When rerun installer, osm_default_subdomain was removed from ansible inventory
The "osm_default_subdomain" option shouldn't be missed in ansible inventory.
Verify this bug with atomic-openshift-utils-3.0.41-1.git.0.2446a82.el7aos.noarch
Once define subdomain during interaction, master_routingconfig_subdomain would be written in installer.cfg.yml. When rerun installer, osm_default_subdomain still could be configured in ansible inventory.
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.