Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1308440

Summary: Failed to add new nodes in native HA env
Product: OpenShift Container Platform Reporter: Gan Huang <ghuang>
Component: InstallerAssignee: Samuel Munilla <smunilla>
Status: CLOSED ERRATA QA Contact: Ma xiaoqiang <xiama>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: aos-bugs, bleanhar, jokerman, mmccomas, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible-3.0.47-1.git.0.4498ce3.el7aos Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-29 12:58:04 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 Gan Huang 2016-02-15 09:07:12 UTC
Description of problem:
When adding new nodes in native HA env, atomic-openshift-installer mistakenly found that lb was currently uninstalled, and it would pass the process of adding new nodes.

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.40-1.git.22.da21865.el7aos.noarch

How reproducible:


Steps to Reproduce:
1.Set up an env of three masters, one node, one lb by atomic-openshift-installer 
2.Add new nodes in above env by atomic-openshift-installer
3.Input "1" to add new nodes

Actual results:
By default the installer only adds new nodes to an installed environment.
Do you want to (1) only add additional nodes or (2) reinstall the existing hosts potentially erasing any custom changes?: 1
10.66.80.80 is already an OpenShift Master
10.66.80.78 is already an OpenShift Node
10.66.80.77 is already an OpenShift Master
10.66.81.78 is already an OpenShift Master
10.66.81.77 is currently uninstalled
Adding additional nodes...
Writing config to: /home/ghuang/.config/openshift/installer.cfg.yml
Ready to run installation process.

If changes are needed please edit the config file above and re-run.

Are you ready to continue? [y/N]: n
Aborted!


Expected results:
Add new nodes successfully in native HA env.

Additional info:

Comment 3 Gan Huang 2016-02-16 06:19:33 UTC
Test with atomic-openshift-utils-3.0.41-1.git.0.2446a82.el7aos.noarch, openshift-ansible-3.0.41-1.git.0.2446a82.el7aos.noarch

The results was the same as bug description.

Installed environment detected.
By default the installer only adds new nodes to an installed environment.
Do you want to (1) only add additional nodes or (2) reinstall the existing hosts potentially erasing any custom changes?: 1
10.66.79.147 is already an OpenShift Master
10.66.79.161 is already an OpenShift Master
10.66.79.158 is already an OpenShift Master
10.66.79.146 is currently uninstalled
Adding additional nodes...
Writing config to: /home/ghuang/.config/openshift/installer.cfg.yml
Ready to run installation process.

If changes are needed please edit the config file above and re-run.

Are you ready to continue? [y/N]: y

PLAY [Populate config host groups] ********************************************

Comment 9 Gan Huang 2016-02-19 06:48:03 UTC
Checked with atomic-openshift-utils-3.0.44-1.git.0.6c50cac.el7aos.noarch.

Test result was the same as bug description.

"callback_facts.yaml" file had been attached.

Comment 19 Gan Huang 2016-02-25 03:21:47 UTC
Verified with atomic-openshift-utils-3.0.47-1.git.0.4498ce3.el7aos.noarch

Test results:
<--snip-->
Gathering information from hosts...
Installed environment detected.
By default the installer only adds new nodes to an installed environment.
Do you want to (1) only add additional nodes or (2) reinstall the existing hosts potentially erasing any custom changes?: 1
10.66.79.124 is already an OpenShift Master
10.66.79.128 is already an OpenShift Master
10.66.79.152 is already an OpenShift Master
10.66.79.138 is already an OpenShift Node



*** New Node Configuration ***

Add new nodes here
<--snip-->

Could add nodes successfully.So move it to verfied.

Comment 21 errata-xmlrpc 2016-02-29 12:58:04 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:0311