Bug 1388754 - [quick install]it should not require LB hostname for non-ha install
Summary: [quick install]it should not require LB hostname for non-ha install
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 05:57 UTC by liujia
Modified: 2017-03-08 18:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously the quick installer would unnecessarily prompt for the name of a load balancer for non HA installations. This question has been removed for single master environments.
Clone Of:
Environment:
Last Closed: 2017-01-18 12:45:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Description liujia 2016-10-26 05:57:26 UTC
Description of problem:
Trigger an quick install, after input one master and one node info and choose no additional node, it will require user to input LB's hostname which mislead user to give usefulness hostname. 

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.4.12-1.git.0.0b5efd2.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. trigger a quick install
# atomic-openshift-installer install
2. after input one master and one node info, choose 'n' for "Do you want to add additional hosts? [y/N]:"
 

Actual results:
It will show following hint:
===========
Setting up high-availability masters requires a load balancing solution.
Please provide the FQDN of a host that will be configured as a proxy. This
can be either an existing load balancer configured to balance all masters on
port 8443 or a new host that will have HAProxy installed on it.

If the host provided is not yet configured, a reference HAProxy load
balancer will be installed. It's important to note that while the rest of the
environment will be fault-tolerant, this reference load balancer will not be.
It can be replaced post-installation with a load balancer with the same
hostname.

Enter hostname or IP address []:
==========

Expected results:
It should not require LB's info for there is only one master specified and just go to nest step about storage.

Additional info:

*** Installation Summary ***

Hosts:
- openshift-136.lab.eng.nay.redhat.com
  - OpenShift master
  - OpenShift node (Unscheduled)
  - Etcd (Embedded)
- openshift-116.lab.eng.nay.redhat.com
  - OpenShift node (Dedicated)

Total OpenShift masters: 1
Total OpenShift nodes: 2

NOTE: Add a total of 3 or more masters to perform an HA installation.

Comment 1 Samuel Munilla 2016-11-03 13:56:08 UTC
https://github.com/openshift/openshift-ansible/pull/2683 makes it clear that we were (optionally) asking if the user wants to override a variable at that stage instead of setting a load balancer.

Comment 3 liujia 2016-11-07 06:26:32 UTC
Version:
atomic-openshift-utils-3.4.17-1.git.0.4698b0c.el7.noarch

Steps:
1. trigger a quick install
# atomic-openshift-installer install
2. after input one master and one node info, choose 'n' for "Do you want to add additional hosts? [y/N]:"

Result:
It will not ask LB hostname and hint as following:
======
You have chosen to install a single master cluster (non-HA).

In a single master cluster, the cluster host name (Ansible variable openshift_master_cluster_public_hostname) is set by default to the host name of the single master. In a multiple master (HA) cluster, the FQDN of a host must be provided that will be configured as a proxy. This could be either an existing load balancer configured to balance all masters on
port 8443 or a new host that would have HAProxy installed on it.

(Optional)
If you want to override the cluster host name now to something other than the default (the host name of the single master), or if you think you might add masters later to become an HA cluster and want to future proof your cluster host name choice, please provide a FQDN. Otherwise, press ENTER to continue and accept the default.

Enter hostname or IP address []: 
======

1) press enter-this step will pass directly and set default value for cluster host name.
2) input a new host-it will set cluster host name as inputted instead of default one.

This new process still have some issues which i commented in bug1339626, for this bug, i think it is verified.

Comment 5 errata-xmlrpc 2017-01-18 12:45:15 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-2017:0066


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