Bug 1497599

Summary:	BuildDefaults are not automatically inherited in master-config.yaml after upgrade
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	Cluster Version Operator	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED CURRENTRELEASE	QA Contact:	liujia <jiajliu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.1	CC:	aos-bugs, fshaikh, jokerman, mgugino, mmariyan, mmccomas, sdodson
Target Milestone:	---
Target Release:	3.9.z
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:	2018-11-29 21:12:26 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 Jaspreet Kaur 2017-10-02 06:51:01 UTC

Description of problem: It is observed that the master config parameters having build defaults are not preserved after upgrade. These build defaults are there to provide proxies to the builds

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results: Builddefaults are wiped off from master config after upgrade to 3.5

Expected results: These parameters should be preserved.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 4 Michael Gugino 2018-11-29 21:12:26 UTC

I believe this is corrected in 3.9 and newer.  If you still face this problem after upgrading to the latest versions, please file a new BZ against the newer version.