Bug 1131167 - oo-install proceeds with install when user has requested quit
Summary: oo-install proceeds with install when user has requested quit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-18 15:17 UTC by Luke Meyer
Modified: 2014-11-03 19:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-03 19:54:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1796 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Enterprise 2.2 Release Advisory 2014-11-04 00:52:02 UTC

Description Luke Meyer 2014-08-18 15:17:57 UTC
Steps to Reproduce:
1. Run oo-install
2. Select deploy OSE
3. Fill in host details
4. Try to quit

Actual results:
Do you want to make any changes to the subscription info in the
configuration file? (y/n/q/?) q

Returning to main menu.
Please wait while your oo-install configuration is validated.

Validating deployment configuration... looks good.

Validating subscription configuration... looks good.

Checking broker.hosts.example.com:
* SSH connection succeeded
* Target host is running Red Hat Enterprise Linux
* Located getenforce... can invoke 'getenforce' with sudo
* SELinux is running in enforcing mode
* Located yum... can invoke 'yum' with sudo

Checking node.hosts.example.com:
* SSH connection succeeded
* Target host is running Red Hat Enterprise Linux
* Located getenforce... can invoke 'getenforce' with sudo
* SELinux is running in enforcing mode
* Located yum... can invoke 'yum' with sudo

Everything looks good. Launching workflow.
Preparing to install OpenShift Enterprise on the following hosts:
  * 10.3.9.251: msgserver, dbserver, broker
  * 10.3.9.249: node
Running 'prepare' step on 10.3.9.251 (broker.hosts.example.com)
...


Expected results:
oo-install saves conf and quits.

Additional info:
You can however Ctrl-C out at this point.

Comment 2 Jason DeTiberus 2014-09-15 16:37:27 UTC
The 2.2 ha installer work will be addressing this as well.

Comment 4 Anping Li 2014-09-25 09:30:35 UTC
Verified and pass 
1) go to main menu when input 'q'
Do you want to make any changes to the subscription info in the
configuration file? (y/n/q/?) q

Returning to main menu.

OpenShift Installer (Build 20140924-1842)
----------------------------------------------------------------------

Welcome to OpenShift.

This installer will guide you through a basic system deployment, based
on one of the scenarios below.

Select from the following installation scenarios.
You can also type '?' for Help or 'q' to Quit:
1. Install OpenShift Enterprise
2. Add a Node to OpenShift Enterprise
Type a selection and press <return>: q
oo-install exited; keeping temporary assets in /tmp/

2) Exit installation when Ctrl+C .
Do you want to make any changes to the subscription info in the
configuration file? (y/n/q/?) ^C
Exiting oo-install at user request.
oo-install exited; keeping temporary assets in /tmp/

3)The configure values are saved.
head .openshift/oo-install-cfg.yml
--- 
Vendor: OpenShift Origin Community
Subscription: 
  type: none
Version: 0.0.1
Name: OpenShift Installer Configuration
Deployment: 
  Global: 
    default_gear_size: small
    broker_hostname:

Comment 5 Luke Meyer 2014-10-23 10:23:08 UTC
Issue resolved with OSE 2.2 installer.

Comment 7 errata-xmlrpc 2014-11-03 19:54:41 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://rhn.redhat.com/errata/RHSA-2014-1796.html


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