Bug 1281717 - atomic-openshift-installer will rerun ansible on master when adding node to existing env with only master detected
atomic-openshift-installer will rerun ansible on master when adding node to e...
Status: CLOSED WONTFIX
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.1.0
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Samuel Munilla
Xiaoli Tian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-13 04:28 EST by Gaoyun Pei
Modified: 2017-08-24 16:50 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-24 16:50:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gaoyun Pei 2015-11-13 04:28:00 EST
Description of problem:
There're two cases this issue would happen:
1. When trying to add new node to an all-in-one env, which only has one host, master&node both running on it.

2. When trying to add new node to a pre-existing env, which contains one master and several nodes, but only master input during the interactive guide or only master configured in the installer.cfg.yml.


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.12-1.git.0.4c09c5b.el7aos.noarch

How reproducible:
always

Steps to Reproduce:
1. As in "Description of problem", add new node to the existing env using "atomic-openshift-installer install".


Actual results:
Installer will run ansible on master and the new node, change the configuration of master to default setting.

Expected results:
atomic-openshift-installer shouldn't change the pre-existing env in any case. 

Additional info:
Comment 1 Brenton Leanhardt 2015-11-13 11:09:17 EST
We should definitely look in to this to make sure there aren't other bugs.  I don't think this should happen for many users.  However, we would like to improve the experience of going from an all-in-one environment to an environment with 1 master and many nodes.

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