Bug 1326198 - The prompt message is not correct in containerized OpenShift installation
Summary: The prompt message is not correct in containerized OpenShift installation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 06:51 UTC by Gan Huang
Modified: 2017-09-06 16:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-06 16:18:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gan Huang 2016-04-12 06:51:00 UTC
Description of problem:
when user exits from the interactive install in containerized OpenShift installation, the prompt message is not correct:
"Edit /var/lib/openshift-installer/installer.cfg with the desired values and run `atomic-openshift-installer --unattended install` to restart the install."
The file /var/lib/openshift-installer/installer.cfg is actually in the container not on the host.

Version-Release number of selected component (if applicable):
openshift3/installer v3.2.0.14

How reproducible:
100%

Steps to Reproduce:
1.docker run -ti -v ~/openshift/:/var/lib/openshift-installer/:Z -v ~/.ssh:/root/.ssh:Z openshift3/installer install
2.Press "n" when asked "Do the above facts look correct? [y/N]:"

Actual results:
Plese confirm that they are correct before moving forward.


10.66.x.x,192.168.0.254,10.66.x.x,test2.novalocal,test2.novalocal

Format:

connect_to,IP,public IP,hostname,public hostname

Notes:
 * The installation host is the hostname from the installer's perspective.
 * The IP of the host should be the internal IP of the instance.
 * The public IP should be the externally accessible IP associated with the instance
 * The hostname should resolve to the internal IP from the instances
   themselves.
 * The public hostname should resolve to the external ip from hosts outside of
   the cloud.

Do the above facts look correct? [y/N]: n

Edit /var/lib/openshift-installer/installer.cfg with the desired values and run `atomic-openshift-installer --unattended install` to restart the install.


Expected results:
The prompt message is correct to guide users to modify the configuration and restart the install. 

Additional info:

Comment 1 Devan Goodwin 2016-04-12 14:20:56 UTC
Yikes this is going to be tough to solve, the installer inside a container cannot really tell what directory you mounted in, the user can specify any host directory they wish.


Note You need to log in before you can comment on or make changes to this bug.