Bug 1400942

Summary:	Master configuration missing after adding new node
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	Installer	Assignee:	Samuel Munilla <smunilla>
Status:	CLOSED WONTFIX	QA Contact:	Johnny Liu <jialiu>
Severity:	low	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	aos-bugs, jkaur, jokerman, mmccomas, smunilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-24 20:50: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:

Description Jaspreet Kaur 2016-12-02 11:18:54 UTC

Description of problem:  Added a new node to the OpenShift cluster using quick installer using below link:

  https://access.redhat.com/documentation/en/openshift-container-platform/3.3/single/installation-and-configuration/#adding-nodes-or-reinstalling-quick

Afterwards, we see some functionality was missing. On investigation we found the master-config.yaml was missing configuration:

[root@t-openshift master]# diff /etc/origin/master/master-config.yaml.109058.2016-11-30@11\:33\:49~ /etc/origin/master/master-config.yaml.43940.2016-11-30@12\:06\:42~ 
9,10d8
<   loggingPublicURL: "https://kibana.logging.example.com/"
<   metricsPublicURL: "https://hawkular-metrics.example.com/hawkular/metrics"
19,20d16
<   extensionScripts:
<     - /etc/origin/master/tech-preview.js
139c135
<   subdomain:  "t-openshift.example.com"
---
>   subdomain:  ""
160,166d155
< jenkinsPipelineConfig:
<   autoProvisionEnabled: true 
<   parameters: null
<   serviceName: jenkins
<   templateName: jenkins-ephemeral
<   templateNamespace: openshift
<


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: The changes made in master config after installation were not there when adding new node using quick installer


Expected results:  The master configuration should be persistent when adding some nodes using quick installer


Additional info:

Comment 1 Samuel Munilla 2016-12-02 20:39:28 UTC

I am unable to reproduce this using the latest version of 3.3 . The scaleup playbook should only gather facts on master hosts and run config only on the new nodes. Could you please provide:

1) the exact version of atomic-openshift-utils you were using
2) installer.cfg.yaml and the ansible inventory produced by the quick installer 

please? I have a theory that the logic somehow tagged this as a reinstall rather than a scaleup.

Comment 2 Jaspreet Kaur 2016-12-05 07:22:36 UTC

Here are the details and attachments :

Installed Packages
Name        : atomic-openshift-utils
Arch        : noarch
Version     : 3.3.50
Release     : 1.git.0.5bdbeaa.el7
Size        : 149 k
Repo        : installed
From repo   : rhel-7-server-ose-3.3-rpms
Summary     : Atomic OpenShift Utilities
URL         : https://github.com/openshift/openshift-ansible
License     : ASL 2.0
Description : Atomic OpenShift Utilities includes
            :  - atomic-openshift-installer
            :  - other utilities

The version customer is on : 3.3.0 and not the latest.