Red Hat Bugzilla – Bug 1281717
atomic-openshift-installer will rerun ansible on master when adding node to existing env with only master detected
Last modified: 2017-08-24 16:50:13 EDT
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:
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.